Opened 4 years ago
Closed 4 years ago
#1713 closed defect (fixed)
chicken-install cache doesn't respect isolation
Reported by: | alicemaz | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 5.3 |
Component: | core tools | Version: | 5.2.0 |
Keywords: | chicken-install | Cc: | |
Estimated difficulty: | easy |
Description
the directory name "chicken-install" is hardcoded in egg-environment.scm. this patch uses the name of the chicken-install binary instead, so that different versions of chicken built with PROGRAM_PREFIX or PROGRAM_SUFFIX have separate caches
different versions with different install locations but the same program names still overlap, but they would overlap in PATH anyway, so this doesn't strike me as a big deal. program prefix/suffix is intended to allow complete isolation of multiple builds tho so separating caches feels obviously correct. (in my own case, I use my distro's packaged chicken for most day-to-day work alongside a prefixed install built from git for messing with chicken itself)
the CHICKEN_EGG_CACHE env var still overrides the default cache location unconditionally, which also seems correct even if it allows multiple versions' caches to merge, since the point of env vars is to enforce something system-wide in all cases invariably
tested on platform=LINUX
Attachments (1)
Change History (2)
Changed 4 years ago by
Attachment: | install-cache.patch added |
---|
comment:1 Changed 4 years ago by
Milestone: | someday → 5.3 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fixed in d61fb34c21