James
James
Hi @peakschris Thanks for reporting. So far, this was intentional. The ``.conanrc`` is intended to be a per-project mechanism, so setting it in the root directory would make it global...
I think this ticket was closed in Conan 2.5 in PR https://github.com/conan-io/conan/pull/16514. Closing the ticket, but please let us know, create new tickets or re-open if this is not the...
Thanks for pointing this out @planetmarshall I agree it would be good to at least add some note in the docs. But I'd like to ask first, just in case....
Hi @planetmarshall Any further feedback here? What do you think would be the best approach, just a note in the docs?
Moving this to the docs repo.
> You might want to use another version in another prefix. Not clear what you mean, could you please clarify what is ``another prefix``?
> The overrides of the dependencies of projectA should not influence the dependencies of projectB. You could have 2 different profiles ``conanfileA_overrides`` and ``conanfileB_overrides`` and you use them when installing...
> That looks useful, though it feels weird to mix dependency issues with profile. this is because an override is considered an exceptional case, kind of graph external configuration, not...
Yes, that is true, but in ``conanfile.py`` is possible also because of historical reasons, the ``[replace_requires]`` is very modern in Conan2.X, while the ``requires(dep, force=True / override=True)`` has been there...
Moving to the docs repo then, thanks for your feedback!