On Saturday, May 19, 2018 at 12:08:22 AM UTC-7, Antonio Rojas wrote: > > > >> OK, so how do we see whether the $SAGE_ROOT/sage script needs to be >> used? Can we just see if $SAGE_ROOT/sage is present and executable and if >> not, use $SAGE_LOCAL/bin/sage? The remark by François seems quite to the >> point: if sage is installed system-wide as a package of python2, then >> invoking python via $SAGE_LOCAL/bin/sage --python is unnecessary overkill. >> Then just calling python2 should be sufficient anyway. >> >> The thing is: the kernel.json does *not* do the right thing out of the >> box if you present it to a system jupyter and$SAGE_LOCAL/bin/sage can't run >> without help. It would be nice if we can get our jupyter kernel >> installation to do the right thing in both cases. >> >> > IMO the right way to fix this would be to make $SAGE_LOCAL/bin/sage not > complain if $SAGE_ROOT is not set (when used to simply launch sage, it > would still be needed for build or install operations). But not sure if > that would currently be possible without major changes. >
So what value does SAGE_ROOT have in the Arch distribution? And what value does it have in sage-on-gentoo? And where does it get its value? The vanilla $SAGE_LOCAL/bin/sage-env only figures out a value if "." or "../.." are good choices (and tests that by the presence of a "sage" file and a "build" directory, so it really ends up depending on its relative location to the "$SAGE_ROOT/sage" script again). -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
