James

If you are putting things in a repo, then you don't name the root folder the "config" folder. The layout of the repo or zip to ``conan config install`` should...

This is related to this: https://github.com/conan-io/conan/pull/10166 I don't like the idiom of checking the local version in the recipes to pull or not a Conan ``tool_requires``, this is why I...

In any case I don't oppose to a ``CMake.get_version()`` or similar helper, I see how it can be useful, and have some recipes a bit cleaner.

Hi @jsallay I think the issue is defining ``self.cpp_info.requires.append("t1::t1")`` in the first place. This feature is only intended and designed to work when ``t1`` package has components defined. Does this...

Thanks for the help, I have managed to reproduce. The issue comes from the definition of: ```python def package_info(self): self.cpp_info.requires.append("t1::comp1") ``` in ``t2``. Note this is a definition for the...

trying it in https://github.com/conan-io/conan/pull/12033, in case you want to test the source branch

Thanks for the feedback, this is exactly the kind of feedback we want for 2.0. The issue happens because 2.0 is filtering out information from dependencies when they are not...

Good hint in existing code: ```python @staticmethod def from_node(node): # TODO: Probably the BINARY_SKIP should be filtered later at the user level, not forced here d = OrderedDict((require, ConanFileInterface(transitive.node.conanfile)) for...

Hi @jsallay I am trying to reproduce this, but it seems that ```python def validate(self): x = self.dependencies["t2"] ``` is working. Are you sure you don't mean the ``generate()`` method...

> Note that duplicating static libraries into potentially several shared libraries is a recipe for disaster when they have global variables. Yes, we know. But there are users (more than...