Opened 12 years ago
Closed 2 years ago
#1113 closed defect (wontfix)
chicken-install -s should not use sudo if it is not necessary
| Reported by: | Christian Kellermann | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | someday | 
| Component: | unknown | Version: | 4.8.x | 
| Keywords: | chicken-install, sudo | Cc: | |
| Estimated difficulty: | hard | 
Description (last modified by )
Currently chicken-install -s unconditionally invokes sudo which installs eggs with root permissions even in the case of local installs, i.e. in your own home directory.
I would expect it to be smarter and use only sudo if the current permissions aren't enough to install an egg.
Change History (4)
comment:1 Changed 11 years ago by
| Description: | modified (diff) | 
|---|
comment:2 Changed 11 years ago by
comment:3 Changed 9 years ago by
| Estimated difficulty: | → hard | 
|---|
comment:4 Changed 2 years ago by
| Resolution: | → wontfix | 
|---|---|
| Status: | new → closed | 
Note: See
        TracTickets for help on using
        tickets.
    
The issue is that a regular Linux user getting chicken from distro packages will have chicken in /usr/bin, but (s)he will not necessarily have all the eggs from distro packages. It's nice to be able to run chicken-install as a normal user. As an egg developer, I do chmod a+w /usr/lib/chicken/7 so that I can install my own eggs frequently. So I don't want to have a pattern of requiring root permission to install every egg, but there are a few that install tools in /usr/bin (chicken-doc and chicken-wrap for example), and that is the only case when I would like chicken-install to use sudo.