Luis Martinez

Agree with @czoido

But we recommend it... why we cant?

You cannot specify a package reference as a requirement in a recipe. Only a recipe reference (with or without revision: `example/1.11@ci/baselines#0`). The package is calculated from the applied settings while...

Thanks for this. I think first we need to try supporting all this into the new `CMakeToolchain` to have native support in Conan.

Then probably shouldn't be documented in the conan docs. Or not like this, I meant we should explore a better integration with the toolchain than using a package with a...

Because the project evolves. Nowadays I wouldn't add `conan-darwin-toolchain` either.

You can use [CONAN_TRACE_FILE](https://docs.conan.io/en/latest/reference/env_vars.html#conan-trace-file) environment variable. Traces will be recorded to a file like: https://docs.conan.io/en/latest/mastering/logging.html#logging-and-debugging This is only Conan 1.X. We don't have something similar in develop2 yet.

Some questions to discuss: So if a package has a regular "require" (with build=False) to another with `i_am_build_context =True` Conan should fail? or this would affect only when the consumer...

I cannot reproduce, Would you mind sending me a recipe and the command you are running?

I see a challenge in both alternatives, we would need to implement it for each generator we need to support, it doesn't look like something that we can make work...