#9622: Check SPKGs more vigorously for common problems
---------------------------+------------------------------------------------
Reporter: mpatel | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone:
Component: packages | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by leif):
We could also formalize/code some aspects of {{{SPKG.txt}}}'s ''Special
Update/Build Instructions'', e.g. in (a) new (optional) script(s) like
{{{spkg-cleanup-upstream}}} (deleting parts not needed by Sage, upstream
repo files, etc.), contained in the spkg itself, and perhaps run
automatically.
Some upstream managers also tend to copy files without preserving mtime,
so we could more or less automatically check for files like
{{{configure}}}, make sure they are newer than their sources, and if not,
touch them before preparing the spkg.
The application of patches to the upstream source tree (i.e. currently
''copying of patched files'') could also be "normalized", allowing to
perform some spkg sanity checks automatically, too, and to simplify
{{{spkg-install}}}s.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9622#comment:4>
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.
