Opened 4 years ago
Closed 11 months ago
#1712 closed enhancement (worksforme)
Incorporate relevant env vars into build cachebusting, maybe
Reported by: | evhan | Owned by: | |
---|---|---|---|
Priority: | not urgent at all | Milestone: | someday |
Component: | unknown | Version: | 5.2.0 |
Keywords: | Cc: | ||
Estimated difficulty: |
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.
Change History (2)
comment:1 Changed 3 years ago by
comment:2 Changed 11 months ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
See
current-status
inegg-compile.scm
. Any changes to those variables will cause rebuild.