James

Hi @parched Thanks for the feedback. The ``` $ conan install . $ conan install . -s build_type=Debug ``` Are mostly to install the different dependencies binaries, but is not...

Hi @AshleighAdams Thanks for the question. There is no way in Conan to select the minimum version. Note that when defining a version range, this is done exactly to be...

Ok, thanks for the feedback. > Regarding the fixed versions, we don't want to use those because we want the packages to be upgradable by downstream consumers, so essentially just...

Thanks for the feedback. I did a further thought about this some time ago. While it does look like manageable by the code shared above, that might be because it...

Hi @Adnn Thanks for your feedback. I think this can be problematic. For example, if the ``conanfile.py`` inside the ``dep1`` folder, contains a ``version = "1.0"`` defined in the recipe,...

Hi @Adnn The PR #18943 adds support to define workspace packages only with ``path: ``, and it will resolve name/version from the recipe itself, that seems to satisfy your use...

> From which recipe will it deduce the version? It will load the reference (version, name, even user/channel) from the recipe. This information can be even dynamically defined by ``set_version()``...

Conan version? Do you have custom ``settings.yml``? If so, please update them. Please provide more details to reproduce that issue. What files, commands are you using? What is the full...

So it seems you are using the cmake-conan integration, this wouldn't be a Conan issue, but a cmake-conan one Moving the ticket to that repo

It seems you are using an outdated ``cmake-conan`` version. Please make sure you are using the latest ``conan_provider.cmake`` and follow the instructions at: https://github.com/conan-io/cmake-conan, including passing the provider with ``-DCMAKE_PROJECT_TOP_LEVEL_INCLUDES=../conan_provider.cmake``