#3537: [with patch] sage-env should set RM="rm -f"
----------------------+-----------------------------------------------------
Reporter: gfurnish | Owner: gfurnish
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.2
Component: build | Resolution:
Keywords: | Author: gfurnish
Upstream: N/A | Reviewer:
Merged: | Work_issues:
----------------------+-----------------------------------------------------
Comment(by leif):
Replying to [comment:8 jdemeyer]:
> Why does `RM` need to be defined at all?
Because
{{{
#!sh
${RM} some_file
}}}
will (hopefully) fail if `RM` is not set or empty?
Imagine `some_file` was executable in that case...
[[BR]]
It would be a bit odd to test and eventually set all such variables
individually in every script that uses some of these, therefore we have
`sage-env`.
Though `CP`, `RM` etc. are meanwhile hardly used within Sage; perhaps
because setting them isn't necessary on any proper OS...
Instead, it would be better to have e.g. `EGREP`, (POSIX-conformant)
`GREP` etc., detected / set by Sage's `configure`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3537#comment:9>
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.
