#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 | Keywords: rd2
Work_issues: | Upstream: N/A
Reviewer: R. Andrew Ohana | Author: Julien Puydt
Merged: | Dependencies:
-------------------------------+--------------------------------------------
Comment(by jdemeyer):
I think the current behaviour is better. I certainly would not expect
{{{
sage --kash
}}}
to run some random `kash` which happens to be installed on my system. I
expect `sage --kash` to run the `kash` from `sage` and give an error
message when `kash` is not installed in Sage.
Replying to [comment:12 Snark]:
> and additionnally, using PATH instead of putting the PATH inside removes
implicit dependencies, which makes sage really more modular (things can
move around and that won't break).
I really don't see the need for this. Maybe you should be more explicit
about the patches on your sleeve.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12627#comment:13>
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.
