If it weren't in the path then you would have to run "make" whenever you want to change one of the scripts in src/bin. This gets boring real quick.
Of course we should copy them to SAGE_LOCAL, a compiled Sage without the src/ folder should work. It sort of does work right now. This is what globally installing Sage should boil down to. On Friday, May 1, 2015 at 6:06:40 PM UTC+2, Nils Bruin wrote: > > To my surprise, $SAGE_ROOT/src/bin is in the path that sage uses and it > appears before $SAGE_ROOT/local/bin . In particular, that means that all > kinds of files in $SAGE_ROOT/local/bin are there just for show, e.g. > sage-ipython etc: for sage execution, only $SAGE_ROOT/src/bin/sage-ipython > is relevant. Why do we even copy them over to local/bin if we're just using > src/bin anyway? > -- 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.
