Summary
Incorporate relevant env vars into build cachebusting, maybe
Metadata
- Id: f8b4973ee9f8f5d4f3f4ee691f3c49a0e7e2315c
- Trac id: 1712
- Type: enhancement
- Reporter: evhan
- Owner:
- Cc:
- Status: closed
- Component: unknown
- Estimated difficulty:
- Resolution: worksforme
- Priority: not urgent at all
- Milestone: someday
- Version: 5.2.0
- Changetime: 2023-11-06 23:24:28 UTC
- Created: 2020-08-06 23:36:27 UTC
- Keywords:
Description
For example, if a user changes CSC_OPTIONS and runs chicken-install again, they presumably want things to be rebuilt. Same goes for CHICKEN_REPOSITORY_PATH, etc.
But then, there are a bunch of other variables that affect builds as well. Where does it end?
It's probably worth considering whether there is a way to consider some environment variables to make caching behaviour more correct, without going totally overboard. For example, we know the set of CHICKEN-defined environment variables that affect builds, that could be where we draw the line. But this needs more thought first.
Changes and comments
[2021-04-26 20:20:43 UTC] felix wrote:
See `current-status` in `egg-compile.scm`. Any changes to those variables will cause rebuild.