James

Yes, the full graph of *recipes* need to be promoted. The binaries are not necessary, but the recipes are needed, as the full graph will always be computed when using...

> I need to expose my whole toolchain (recipes) to my users/customers (which use "conan install pkgA"). Yes, it is true, the recipes need to be available to resolve a...

To follow up on this: - Making dependencies optional is still totally possible in Conan 2, and it can be done easily for ``test_requires`` for example, if we know what...

Actually, I think at the light of the ``vendor`` feature that something more could be done to improve this. I am re-opening and assigning to 2.5 for research it

I am exploring in https://github.com/conan-io/conan/pull/17117 the possibility to completely skip ``test_requires`` and ``tool_requires`` from graphs with a new ``tools.graph:skip_build`` config, feedback very welcome.

Hi all This was closed by https://github.com/conan-io/conan/pull/17117, that added new ``tools.graph:skip_build`` and ``tools.graph:skip_test`` confs to be able to optimize and avoid the resolution of build and test requires respectively. It...

Hi @zflat Thanks for your question. I agree that that sentence is not very clear. It refers to the ``test_package/conanfile.py`` code: ```python def build(self): cmake = CMake(self) cmake.configure() cmake.build() def...

I am investigating in https://github.com/conan-io/conan/pull/16443 if it is possible to allow this, or ``replace_requires`` requires full referential transparency. Even with this investigation can improve things a bit on the Conan...

@AbrilRBS has also been investigating the part of the ``cpp_info.requires``, we are doing progress, but still need more research.

https://github.com/conan-io/conan/pull/16443 has been merged, it will be in next 2.8 release. It should cover the cases of referential transparency for ``self.dependencies[]`` and ``cpp_info.requires`` checks. For CMake targets and similar stuff,...