Le 12/01/2012 16:08, Michael Orlitzky a écrit :
On 01/11/12 23:10, William Stein wrote:
On Wednesday, January 11, 2012, Michael Orlitzky<mich...@orlitzky.com
<mailto:mich...@orlitzky.com>> wrote:
On 01/11/2012 03:40 AM, Jeroen Demeyer wrote:
True, but we're talking a different order of magnitude here. Speeding
up the atlas installation by just 5% would save more time than removing
both bzip2 and patch.
If we want to be sure that the user has bzip2 installed, we should
just bzip the source tarballs =)
We also *need* the bzip2 devel library and headers so that the Python
bzip2 module gets built.
Oh that wasn't really a serious suggestion: it makes the set of sage
users (A) equal to the set of sage users with bzip2 installed (B), sure,
but it does so by eliminating the users (A-B).
I notice that :
(1) to unpack the sage sources, you need tar ;
(2) once you have unpacked it, you need tar+gunzip to unpack
spkg/base/bzip2-1.0.5.tar.gz
So users of sage already have tar+gz anyway...
Snark
--
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
