#12627: The spkg/bin/sage script engraves paths to executables
--------------------------------+-------------------------------------------
Reporter: Snark | Owner: leif
Type: defect | Status: needs_info
Priority: major | Milestone: sage-5.0
Component: scripts | Resolution:
Keywords: rd2 | Work issues:
Report Upstream: N/A | Reviewers: R. Andrew Ohana
Authors: Julien Puydt | Merged in:
Dependencies: | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by jdemeyer):
Replying to [comment:16 Snark]:
> Sigh.
>
> First, you still mention "test -x" although I pointed out it's not the
recommended way to check for an executable.
You "pointed out" without saying why. I think `test -x` is used perfectly
here.
> Second, as I already pointed out, my patch makes sage run sage versions
by default if available. And if not available in sage, if they are
available on the system, use that. The only error case is the one where
indeed, it is really not available.
As I (and leif, for once I agree with him) have said, sage --COMMAND is
supposed to run the Sage version of COMMAND.
> There seem to be a high dose of paranoia in sage developers about
everything that doesn't come out of sage.
That's not really the point. Within Sage, we have more control over the
versions of the optional packages. Also, nothing prevents you from
running in a shell (either a Sage shell or not):
{{{
$ kash
}}}
It's as easy as that.
> My point is simple : from a sage-whatever-beta_n to sage-whatever-
beta_{n+1}, 90% of the spkg are the same. So if I could make foo-3.14.spkg
install in $HOME/sage/foo-3.14 and make the rest of sage use that (this is
modularity -- the contrary of a one-block where nothing can move an hair's
width without everything collapsing), then that means I can gain 90% of
build time. And I have the room to have more versions of sage installed
simultaneously.
You could play with environment variables to solve this: apply patch
#12647 and write in your `.sage/sagerc`:
{{{
export PATH="$PATH:$HOME/sage/foo-3.14/local/bin"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$HOME/sage/foo-3.14/local/lib"
}}}
or something like this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12627#comment:17>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
