James

Lets get some feedback from the Tribe, to see if we are missing some use cases.

I am drafting https://github.com/conan-io/conan/pull/12253 to discuss it, to be introduced in 1.54, as it would be necessary for the migration if we are removing ``build_policy = "always"``

Backport in https://github.com/conan-io/conan/pull/11936 merged, so this will be in next 1.52

> How this relates to: https://docs.conan.io/en/latest/developing_packages/package_dev_flow.html#package-dev-flow where we can provide --source-folder explicitly (different than the one hardcoded in layout())? The docs in https://docs.conan.io/en/latest/developing_packages/package_dev_flow.html#package-dev-flow are legacy, they were written before the...

Hi @derived-coder Sorry, it is not clear what you mean. CMakeToolchain already has a block to define all ``CMAKE_INSTALL_PREFIX`` and family. You need to do a full report, specifying a...

Hi @TaylorEllington The first part is doable, and it doesn't have big risk, as it would be an opt-in. Feel free to do a PR if you want, though it...

> To clarify, are you saying that with the advent of Conan 2.0, my intended use paradigm will no longer work? We are just now looking into adopting Conan, but...

> Out of curiosity, what is the timeline for 2.0? I couldn't find a launch target on the wiki. We will release 2.0-beta.2 shortly, and we expect at least 2-3...

@TaylorEllington This seems related to missing ``--hidden-imports`` in the ``pyinstaller.py``. They have been added recently for minor ``1.51.2`` patch release, if you want to update and try again.

Hi @Facon With new tooling is: ```python def package_info(self): self.buildenv_info.append_path("PATH", ) # where path can do os.path.join(self.package_folder, ...) for example ``` Then on the consumer side, use the ``VirtualBuildEnv`` generator....