On Tue, Jun 29, 2010 at 5:25 PM, Tim Daly <[email protected]> wrote: > 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?
This is basically what happens, except instead of using patch to change the source code in place, the patched file is "pre-computed" and then just copied over. This avoids having patch as a requirement on the machines that Sage is building on. > 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. For better or worse, a long time ago it was decided that patch was not a prerequisite which is why things are the way they are now. > 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. They are used in the spkgs and all over http://trac.sagemath.org/ --Mike -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
