#9419: Update Developers Guide to state how patches should be made.
-----------------------------+----------------------------------------------
Reporter: drkirkby | Owner: mvngu
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.7.1
Component: documentation | Keywords: patch doc howto spkgs diff
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:9 drkirkby]:
> One thing we need to be careful of is that when testing the patch,
people don't overwrite the src directory. Which makes me think, should the
write permissions for all files below src be removed? That would at least
prevent that accident, though perhaps it would screw up some packages.
Well, you usually ''want (or need) to overwrite / modify'' files in `src/`
when applying patches from within `spkg-install`...
Note that you don't need write permissions on a file you're going to
patch, but on its containing directory.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9419#comment:11>
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.
