I will look at the tinyclos egg, but I think you should use -install-prefix for what you are trying to do. I have started using that for my Debian scripts and so far it seems to work well. I haven't tried anything with tinyclos yet, though. The idea is that you should _not_ have to add any workarounds: the express purpose of the -install-prefix option is for sandbox-type installation.
-Ivan "Leonardo Valeri Manera" <[EMAIL PROTECTED]> writes: > On 02/03/2008, Ivan Raikov <[EMAIL PROTECTED]> wrote: >> >> What you are referring to is the _Chicken_ install prefix, >> i.e. where the Chicken executables are installed. What I am referring >> to, is the user _install_ prefix, for situations where you would like >> have the eggs in a separate directory hierarchy (e.g. when building >> binary packages). It is a bit confusing, but take a look and the >> updated chicken-setup documentation and let me know what you think. I >> have already made the changes, but of course I can make further >> changes. > > I still have the same issue when installing tinyclos (release) with > trunk chicken. > > I need to know whether I need to add functions to take care of eggs > that do not respect -R, or what :) > > Cheers, > Leo _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-hackers