Hi Matt, On Sun, 15 Jun 2014 10:41:07 -0600 Matt Gushee <[email protected]> wrote:
> Hi, Manfred-- > > On Sun, Jun 15, 2014 at 9:40 AM, Manfred Lotz <[email protected]> > wrote: > > On Sun, 15 Jun 2014 14:51:50 +0400 > > Oleg Kolosov <[email protected]> wrote: > > > >> On 06/15/14 13:28, Manfred Lotz wrote: > > >> > Question: Could I point chicken to a directory in $HOME where my > >> > egg installations could go to? > >> > >> # exact path is irrelevant as long as you can write to it > >> mkdir -p $HOME/.local/lib/chicken > >> chicken-install -init $HOME/.local/lib/chicken > >> export CHICKEN_REPOSITORY=$HOME/.local/lib/chicken > >> > >> chicken-install numbers > >> > >> Add "export CHICKEN_REPOSITORY ..." command to .bashrc or kde env > >> or so to persist. > > > > Great. This is what I was looking for. Thanks a lot. > > However, there is one problem with this method (I think--it's been > several years since I tried to do this). A few eggs install > executables, and even if you change the repository path, > chicken-install will still try to place them under the same prefix > where chicken itself is located (presumably /usr/bin in your case). I > don't know of a solution to this problem. I also like to keep > non-package-manager files out of the /usr hierarchy, but this is a > case where I cheat. But maybe there is some hack that will trick > chicken-install into placing the executables somewhere else. If so, > I'd like to know too. > I fully agree. This would be important to have. If currently not possible perhaps chicken-install could be enhanced to be able to place executables somewhere else. -- Manfred _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
