#16048: dev docs: Inclusion Procedure for New and Updated Packages
-------------------------------------+-------------------------------------
Reporter: rws | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Ralf Stephan | Reviewers:
Report Upstream: N/A | Work issues:
Branch: public/spkg- | Commit:
devdoc | 77ce76e58c464472313c9836f08c31a8e1836c82
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Does having both a SPKG and a build/pkg/foo directory work? Which spkg-
install script is being used? I don't even know if this works, but it
shouldn't. You can either have a legacy spkg or make a git branch with an
upstream tarball (gz/bz2).
--
Ticket URL: <http://trac.sagemath.org/ticket/16048#comment:8>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
