[feature] Profile include precedence

[jasal82]

What is your suggestion?

Currently the include mechanism seems to always prefer files in the $CONAN_HOME/profiles directory. Imagine the following situation:

• We have a base profile base and a profile profile in $CONAN_HOME/profiles
• The profile profile has a statement include(base)
• When referencing the profile using -pr:h profile in a Conan command, the files are consumed as expected

But if we have a local snapshot of these profiles (both base and profile) in another directory (let's call that /path) and we reference the profile there using -pr:h /path/profile then Conan always includes the base file in $CONAN_HOME/profiles and not the one in /path.

I'd like to request a change of that behaviour. Conan should try to find the include in the directory of the parent profile first and then fall back to CONAN_HOME. If that cannot be made default for whatever reason, it could be added behind an opt-in via global.conf setting.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

[jasal82]

I looked into the code and found that include(./base) works in this case. However, this is rather surprising (because usually ./x is considered equal to x) and not currently documented.