On Fri, May 02, 2014 at 09:48:50AM +0000, Francois Bissey wrote: > I know what you want to say Felix but once the pre-requisite are in place > we are more less performing all the install from a "sage shell" in which > sage-env is used to set the environment.
a sage shell is not necessary to run the spkg-install's (see my proof-of-concept thing). and it shoudn't be used. likewise, any of the other package managers proposed back then (ebuilds-based?) wouldnt be ran from a sage-shell. > When spkg-install is at work, sage-env is read. At least that's how I > understand > it works. part of the problem. i've fixed this by *not* sourcing sage-env from toplevel, see the demo tarball. good luck with this. 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.
