#10118: upgrade sphinx to version 1.0.4
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: tbd
Type: enhancement | Status: needs_review
Priority: blocker | Milestone: sage-4.6.1
Component: packages | Keywords: sphinx spkg
Author: Minh Van Nguyen | Upstream: N/A
Reviewer: Jeroen Demeyer | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by jdemeyer):
Replying to [comment:17 jhpalmieri]:
> I don't think this is the usual practice for spkgs.
I agree that this is not the usual practice, but maybe we should make it
usual practice? (I've done it for {{{pari}}} and {{{ecm}}}) The point is
that I see absolutely no reason to put '''patched''' files under revision
control. Putting the '''patches''' (i.e. the diffs) under revision
control makes sense (and that's also what I did). One advantage is that
you get smaller diffs between spkg versions. Also the spkgs themselves
should be smaller. Putting patched files under revision control is almost
the same as putting {{{src/}}} under revision control and we don't do that
either...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10118#comment:18>
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.
