Opened 7 years ago
Closed 6 years ago
#1608 closed defect (fixed)
chicken-install checks for installed files even when -n is passed
| Reported by: | Vasilij Schneidermann | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.1 |
| Component: | core tools | Version: | 5.0.0 |
| Keywords: | chicken-install | Cc: | |
| Estimated difficulty: | trivial |
Description
I've discovered chicken-install -n for fetching dependencies and building programs without actually installing them. Unfortunately chicken-install refuses building programs if such a program has been installed before, despite passing an option to not install anything.
I've attached a simple fix that moves the check right before actually installing the files.
Attachments (1)
Change History (5)
Changed 7 years ago by
| Attachment: | 0001-Check-for-installed-files-iff-installing-them.patch added |
|---|
comment:1 Changed 7 years ago by
| Milestone: | someday → 5.1 |
|---|
comment:2 Changed 6 years ago by
comment:3 Changed 6 years ago by
Note that the egg's name must be different from the egg that originally installed the program or library that you're building in the new egg.
Note: See
TracTickets for help on using
tickets.
Clarification: The conflict situation happens if you have two different eggs that provide the same file. Suppose you install an elephantdb egg providing a createdb program and build a personal-stuff egg providing a createdb program, too. Installing the former works fine, building the latter doesn't. The change I propose here would allow building the latter, but still prevent you from installing the latter.