#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 drkirkby):
Replying to [comment:1 mpatel]:
> Possibilities, some of which could simply give warnings or reminders:
>
> * Check for `spkg-check` and `spkg-install` and that they're
executable.
Good idea
> * Check the first line of scripts for `#!/usr/bin/env` (cf. #9597).
Yes.
> * Check for an unfinished Mercurial patch queue.
Yes
> * Check for the presence of `set -e`.
William will not have that. He is very against the use of set -e.
> * Check for the presence of $MAKE and other important variables.
What's important in one package is not in another. That might be difficult
to do.
> * Check for Python scripts and whether Python is a dependency in
`spkg/standard/deps` (cf. #9435, #9507).
>
> I'm sure there are others!
If the package is called foobar-x.y.z, then SPKG.txt should have the
string foobar.x.y.z somewhere in it. Many times commits get made, with no
entry in SPKG.txt
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9622#comment:6>
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.
