Proposal: 1) In sage-env, do not add $SAGE_ROOT to the $PATH. 2) Rename local/bin/sage-sage to local/bin/sage
Reason: The python 2.7.2 package checks whether hg is available and runs hg during the build process. Now imagine you have a system-wide Sage install. Then hg is found in /usr/local/bin/hg, which is just a script to execute sage --hg "$@". But now "sage" is found in SAGE_ROOT, the sage we are just installing. Running this obviously fails because we have not finished building sage. If SAGE_ROOT would not be in the PATH, then SAGE_ROOT/sage would not be executed, instead the intended /usr/local/bin/sage would be executed. In order to make constructs like "sage --foo" still work from within various scripts, we still need a "sage" executable in the PATH within a finished Sage installation. So that explains the second part of my proposal: rename sage-sage to sage. Jeroen. -- 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
