James

Thanks very much all of you for the feedback and the data. I have been thoroughly consider our options, and at the moment we are not considering this feature: Yes,...

Closing, at the moment this will not be considered.

Hi @DS-Serafin But have you read the above rationale, that made us close this issue? We know this can be slow in some cases, but the thing is that a...

Thanks for the feedback @fschoenm > Would it be possible/useful to change test()/ctest() to only run if can_run() returns True? I think it might work well together with other config...

Hi @andrey-zherikov Thanks for your suggestion. > Reading through [CI tutorial](https://docs.conan.io/2/ci_tutorial/products_pipeline/full_pipeline.html) I noticed that conan expects users to call conan lock create for every package for every configuration. This is...

> I'm not sure I got you right. IMHO any package list is a dependency graph, however the latter might consist of multiple isolated subgraphs which is fine. ``` conan...

> for pkg in $pkg_list; do conan lock create --requires=$pkg ...; done This is doable without iteration with: ``` conan lock create --requires=zlib/1.3.1 --requires="bzip2/[*]" --requires=... ```

Hi @MrF-31337 Thanks for the feedback. I think this seems a limitation of the ``cmake-conan`` (or CMake in general) approach. This use case should work better with the canonical flow...

I am not sure if I understand. Conan 1 never used the ``cmake_file_name`` in any of the qbs generators, not the legacy ``qbs`` one, not in ``QbsProfile``. The JSON generator...

Hi @ABBAPOH It seems this PR went stale, did you check the above comment? The main issue seemed the abuse of a ``cmake_xxxx`` property for the ``qbs`` generators, and how...