#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 leif):
Replying to [comment:20 Snark]:
> I ran "make ptestlong" and it tried to run things using "sage
--something".
>
> Kash wasn't the problem ; I don't remember if it was ecl or scons... or
something else... Of course the test failed : even though I made sure in
sage-env it had what it takes in the PATH, the script didn't even see it!
>
> I claim sage-as-it-is is broken because it can't accept a small change
in a place without breaking in an unrelated place for no serious reason.
Not in an "unrelated place", nor for no reason: `ptestlong` checks whether
the installation went (or is still) ok, and testing whether programs
installed by Sage ''are'' where they belong (or have been installed), and
whether they work, is just part of that.
If you change their locations, you'd obviously also have to change these
tests.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12627#comment:22>
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.
