#9622: Check SPKGs more vigorously for common problems
------------------------+---------------------------------------------------
Reporter: mpatel | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone:
Component: packages | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by leif):
Yep, but two comments:
* I wonder how many people actually use {{{sage-pkg}}} to create spkgs
(rather than just use {{{tar}}}).
* In a perfect world, the reviewer(s) would do this job (i.e. look at the
code e.g., too, not just try to install a new package and then give
positive review, or sometimes the other way around).
I was thinking of a good spkg template ({{{-install}}}, {{{-check}}},
{{{SPKG.txt}}}), too. And perhaps some minimalistic shell programming
guide targeted at Sage scripts.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9622#comment:2>
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.
