[feature] Add --build parameter to build all packages not in local cache
See original GitHub issueOn our Linux CI/CD server I want to prevent that we download binary packages that are built against a newer libc version.
The easiest solution for that seems to build all packages that are not in the local cache from source. However as fas as I can find the --build option for conan install, conan create etc doesn’t support this build policy yet.
I think it would be useful to allow conan install .... --build=not_in_cache. The not_in_cache parameter is of course only an example and can be changed as fit.
- I’ve read the CONTRIBUTING guide.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Managing the global packages, cache, and temp folders
In this article. Viewing folder locations; Clearing local folders; Troubleshooting errors. Whenever you install, update, or restore a package, ...
Read more >conan create — conan 1.55.0 documentation
Possible parameters: --build Force build for all packages, do not use binary ... of the dependencies exists there, it will install those in...
Read more >Build caching in AWS CodeBuild
Local caching stores a cache locally on a build host that is available to that build host only. This is a good option...
Read more >Build Cache - Gradle User Manual
The Gradle build cache is a cache mechanism that aims to save time by reusing outputs produced by other builds. The build cache...
Read more >Caching dependencies to speed up workflows - GitHub Docs
Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks. We already have a repo for
conan config install, I will add our settings.yml to it.Hi @wdobbe
I think the right, long term solution if you want to control, track and manage properly the differences of the new libc version is not this way, but adding a custom sub-setting that will represent this difference: https://docs.conan.io/en/latest/extending/custom_settings.html#adding-new-sub-settings.
This can be very straightforward, only add the subsetting to the settings.yml, then to the profiles that you are using, no need to change the recipes, and if you want to have backward binary package_id compatibility, adding a
Nonevalue for the subsetting will make it. Then--build=missingwill always do the right thing, safely and optimally.