#20692: Add sage-apply-patches helper script for use in spkg-install scripts
-------------------------------------+-------------------------------------
Reporter: embray | Owner:
Type: enhancement | Status: needs_work
Priority: minor | Milestone: sage-7.3
Component: build | Resolution:
Keywords: | Merged in:
Authors: Erik Bray | Reviewers: Jeroen Demeyer
Report Upstream: N/A | Work issues:
Branch: u/embray/patch- | Commit:
cleanup | 29bd19903b16289c178e9468194318e5d1017dad
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by embray):
Those scripts are only ever in spkg directories though and are specific to
each spkg. They are not in bin/ paths added to `$PATH`. This is a helper
script used in installation like the rest in build/bin, all of which
(sensibly) start with `sage-`.
I'm probably also going to add a `sage-spkg-python` (or something, I don't
care what it's called) that will be exec'd by the `spkg-install` for most
Python packages since the vast majority of them are cookie-cutter anyways
(especially if you also want to have every one of them calling `whatever-
apply-patches` by default). This would be to provide a solution for
#16897 which also calls out this fact. (I think it's important for every
package to have a file called `spkg-install`, but it's fine if its sole
function is to call some other generic script).
--
Ticket URL: <http://trac.sagemath.org/ticket/20692#comment:15>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
