On Mon, Mar 10, 2014 at 09:12:18AM +0100, Ralf Hemmecke wrote: > I don't know whether this is the right place to ask, but how can meet > Sage the following use case? > > - system-wide installation of sage in /opt/sage/$SAGEVERSION > - /opt/sage is not writable by an ordinary user > - "sage -i PACKAGE" exacuted as an ordinary user should install an > additional spkg into $HOME/.sage-local/$SAGEVERSION. > > Is that currently possible? > Can such behaviour be easily achieved? > > Of course, I don't want to copy the full installation of Sage, but > rather only the files that "sage -i" needs to modify are copied over to > $HOME. And I would expect that Sage first looks into > $HOME/.sage-local/$SAGEVERSION before it tries /opt/sage/$SAGEVERSION.
when I was working on the spkg-install scripts, i decided to undisambiguate SAGE_LOCAL. SAGE_LOCAL is used as "installation" path *and* as search path from within the spkg-install's. between the lines of #15136 #14804 i fixed this by introducing a SAGE_PREFIX variable. this then was supposed to be passed as an ordinary prefix to the spkg-install programs and was set to $SAGE_LOCAL for inside-sage-the-distribution (or git-development-mode, how-you-call-it) installs. i'd be happy to see (something like) SAGE_PREFIX (maybe just PREFIX?) in future versions. i'm sorry i currently don't have a lot of (read: "no") time to work on this. good luck felix -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
