>> So there are three things >> 1. "sage" should be the only entry point for any non-developer. >> 2. $SAGE_ROOT/local/bin is not known to non-developers. >> 3. Inside $SAGE_ROOT/local/bin scripts can assume a proper environment. > > I think this is a good suggestion.
Would there be interest in the following workflow for installing sage. a) Get the sage tarball b) extract the tarbal to SOMEDIR c) cd SOMEDIR d) configure (with or without --prefix) e) make f) make install I'm not so sure whether I'd like to copy the whole of sage into the --prefix directory, but one should consider the option of --exec-prefix to specify a place where the "sage" script would be copied to. Since there is a configure step, the "sage" script would exactly know where the SAGE_ROOT is. No guessing. I'm not (yet) too much into sage, and I don't know whether this complicates things more for novice sage users, so consider this just as a contribution to a discussion. I'd also like to learn how things actually work. Ralf --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
