Opened 11 years ago
Closed 9 years ago
#1144 closed enhancement (fixed)
chicken-install's -keep-installed and -prefix/-deploy options don't play nicely together
| Reported by: | evhan | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 4.12.0 |
| Component: | core tools | Version: | 4.9.x |
| Keywords: | chicken-install, extensions | Cc: | |
| Estimated difficulty: | medium |
Description
It would be ideal if the -keep-installed option to chicken-install respected -prefix/-deploy.
Currently, -keep-installed only considers eggs in the "normal" repository to be installed, regardless of whether it's given a -prefix argument. So, any eggs already installed there will be skipped (incorrectly) on chicken-install -deploy -prefix foo ..., and any eggs not installed there will be fetched and reinstalled under foo/ on each invocation.
I think the options should respect one another, so that the following commands should result in the egg foo being downloaded and installed once, whether or not it's already installed in the normal repository:
$ chicken-install -deploy -prefix bar -keep-installed foo # ... should download and install foo $ chicken-install -deploy -prefix bar -keep-installed foo # ... should do nothing
Change History (4)
comment:1 Changed 11 years ago by
| Priority: | major → minor |
|---|
comment:2 Changed 10 years ago by
| Milestone: | someday → 4.12.0 |
|---|
comment:3 Changed 9 years ago by
| Estimated difficulty: | → medium |
|---|
comment:4 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed for 4.11.2 by 936b17f9.

Strangely this wasn't addressed by 24b0ce85ca5cb8881155d4a9834a4b036d1701da / c24fcb6f525fa795afeaaf0a94f587518c0ae2e1 but the fix should look a lot like those.