On 11/13/10 10:33 AM, Jeroen Demeyer wrote:
On 2010-11-13 05:32, Robert Bradshaw wrote:
I think the solution everyone liked was either making patch a
dependency or spkgs, and using something like quilt. The current
situation of copying files and/or manually maintaining patches is a
pain and has several drawbacks.
Is there a reason why we don't include GNU patch as a spkg, or it is
just a matter of "nobody ever did it"?
For the pari spkg (remember #9343?), I actually automated the process of
generating patched files from the patches in a file spkg-make. This was
really needed, because there were like 10 patches or so and I was making
a new spkg at least once per day...
Jeroen.
I did it a few months ago
http://boxen.math.washington.edu/home/kirkby/patches/patch-2.6.1.spkg
William was against including it, though there was a concensus it should be
included, so William accepted it. But there were still many arguments about it,
and I've never put the package up for review. But I did create it some months back.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
