#9419: Update Developers Guide to state how patches should be made.
-----------------------------+----------------------------------------------
Reporter: drkirkby | Owner: mvngu
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-4.7.1
Component: documentation | Keywords: patch doc howto spkgs diff
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-----------------------------+----------------------------------------------
Changes (by leif):
* status: new => needs_info
Comment:
Ok, I just started rewriting
`doc/en/developer/{producing,patching}_spkgs.rst`.
'''Q:''' Should patches to upstream source (also? optionally?) be
documented in `patches/README.txt` or whatever it is called, or just -
i.e. only - in `SPKG.txt`'s ''Special Update/Build Instructions'' section
(or even a new one, "''Patches''")?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9419#comment:13>
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.
