James

Ok, I have checked this. The above alternative is only feasible at the moment for ``tool_requires`` (with ``build=True``), in the "build" context otherwise for regular requires it is not possible....

The repackage feature, that has been renamed to "vendor" (vendoring dependencies) has been merged in https://github.com/conan-io/conan/pull/16073, for next Conan 2.4 (hopefully released today).

Hi @skoolkid Thanks for your question. To define configuration items, they no longer go to ``conan.conf`` (what ``conan config set`` did), because that file was removed in Conan 2.0. The...

> Thanks for the response. I've added -c options to my conan install and conan build commands to define both tools.microsoft.bash:subsystem and tools.microsoft.bash:path, but now the build fails with this...

Lets try to have a repro case, otherwise it is going to be challenging to investigate this. This is what I am doing: - I have this conanfile.py: ```python from...

> That's easier said than done, because my system is a GitHub runner with msys2 installed by [msys2/setup-msys2](https://github.com/msys2/setup-msys2). In case you are not aware, there is a ``msys2/cci.latest`` package in...

Hi @sagi-ottopia Thanks for your question, it is good one. Indeed using ``channel`` is no longer recommended. The main challenge is that you need to modify the ``requires = ``...

You can find some info in https://docs.conan.io/2/tutorial/versioning/version_ranges.html#semantic-versioning Pre-releases and build-metadata are not the same, very different. To use pre-releases they should be explicitly opted-in, in the version-range itself, or in...

I'd recommend carefully reading the discussions in https://github.com/conan-io/conan/issues/15638, I think they are very related. > Just to be sure, all I have to do is to modify my set_version function...

Sure, @opajonk, that is a related question, but slightly different. When you create different versions or revisions of a given package (A), then you want to test those changes in...