Perhaps I'm being thick about this. In Axiom's build
we have a zip file for GCL source code. At build time
we unzip the GCL source, THEN apply our patches, THEN
we do a build.
Why wouldn't this process work in Sage?
Sage requires all of GCC to be installed.
Surely requiring patch is not a lot more overhead.
In the worst case, add the source for patch and build
your own copy early in the build process.
Sending/posting/trading "diff -Naur" patches is a long
standing tradition in open source. Sage is the only
project I've ever heard of that doesn't use them.
Mike Hansen wrote:
On Tue, Jun 29, 2010 at 4:54 PM, Tim Daly <d...@axiom-developer.org> wrote:
I'm surprised you don't use patch.
Mercurial can generate patches.
The issue is not generating the patches -- it's applying them. All of
the spkgs (should) have the diff as well as the file with the patch
applied.
--Mike
--
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
