On 20 April 2015 at 02:16, John H Palmieri <jhpalmier...@gmail.com> wrote: > As far as I can tell, it is never a good idea to set SAGE_ROOT, nor is it > ever suggested that you do so in the documentation. I think you could expect > things to break if you set environment variables which Sage uses internally. > One solution is to create a link '/usr/local/bin/sage' pointing to the > executable sage script in SAGE_ROOT, whatever that happens to be. Then make > sure that /usr/local/bin is in your PATH.
THat is what I do (for system-wide installs, I have something else for current working development versions). I also use sagetex without any use of SAGE_ROOT. John > > Probably we should put a warning in the documentation that users should not > set SAGE_ROOT, or at least if they set it, then they might run into > problems. > > John > > > > > On Sunday, April 19, 2015 at 2:23:09 PM UTC-7, ggrafendorfer wrote: >> >> Sagetex e.g., is one reason: >> >> http://www.sagemath.org/doc/installation/sagetex.html >> >> Georg >> >> On Sunday, April 19, 2015 at 6:43:27 PM UTC+2, John Cremona wrote: >>> >>> Do you have a reason for having SAGE_ROOT set at all? I don't. >>> >>> John >>> >>> On 19 April 2015 at 17:33, ggrafendorfer <georg.gra...@gmail.com> wrote: >>> > Hi >>> > >>> > When I build a new version of sage in a separate directory, and then, >>> > while >>> > beeing in that directory, execute >>> > >>> > ./sage >>> > >>> > then the current "old" version of sage, which can be found in SAGE_ROOT >>> > is >>> > executed. >>> > E.g., this looks as follows: >>> > >>> > .../data/sage-6.6$ pwd >>> > /mnt/data/sage-6.6 >>> > .../data/sage-6.6$ ./sage >>> > ┌────────────────────────────────────────────────────────────────────┐ >>> > │ Sage Version 6.4.1, Release Date: 2014-11-23 │ >>> > │ Type "notebook()" for the browser-based notebook interface. │ >>> > │ Type "help()" for help. │ >>> > └────────────────────────────────────────────────────────────────────┘ >>> > sage: >>> > >>> > after changing the path name SAGE_ROOT points to, such that SAGE_ROOT >>> > does >>> > not exist anymore, the following behaviour shows up (SAGE_ROOT is set >>> > to >>> > /mnt/software/sage): >>> > >>> > .../data/sage-6.6$ ./sage >>> > ./sage: line 118: cd: /mnt/software/sage: No such file or directory >>> > ./sage: cannot determine SAGE_ROOT directory >>> > >>> > Isn't that strange!? This imposes the common question "Is this a bug or >>> > a >>> > feature?" >>> > >>> > However, indeed it is the case that when doing >>> > >>> > .../data/sage-6.6$ make ptestlong >>> > >>> > that the whole test is done with sage 6.4.1 instead of sage 6.6!! >>> > While SAGE_ROOT still pointing to a non-existing directory: >>> > >>> > .../data/sage-6.6$ make ptestlong >>> > cd build && \ >>> > "../build/pipestatus" \ >>> > "env SAGE_PARALLEL_SPKG_BUILD='' ./install all 2>&1" \ >>> > "tee -a ../logs/install.log" >>> > Nothing to (re)build / all up-to-date. >>> > ./sage -b >>> > ./sage: line 118: cd: /mnt/software/sage: No such file or directory >>> > ./sage: cannot determine SAGE_ROOT directory >>> > Makefile:19: recipe for target 'build' failed >>> > make: *** [build] Error 1 >>> > >>> > after changing the according path name, such that SAGE_ROOT exists >>> > again, >>> > >>> > .../data/sage-6.6$ make ptestlong >>> > >>> > works again, and is executed with sage-6.4.1, which is definitely NOT >>> > WHAT >>> > ONE WOULD EXPECT in this case, I would say, or am I wrong? >>> > >>> > >>> > My usual workflow is that I build the new version of sage, the execute >>> > make >>> > ptestlong, and after that I copy the new built version to SAGE_ROOT, >>> > replacing the old one there. >>> > >>> > >>> > greetings, Georg >>> > >>> > >>> > >>> > -- >>> > 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+...@googlegroups.com. >>> > To post to this group, send email to sage-...@googlegroups.com. >>> > Visit this group at http://groups.google.com/group/sage-devel. >>> > For more options, visit https://groups.google.com/d/optout. > > -- > 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. -- 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.
