Nils Bruin wrote:
On Mar 28, 9:10 pm, William Stein <wst...@gmail.com> wrote:
I'm for allowing the use of Python in the Sage build system.
It seems to me that with a little care one could have python used in
some parts of the build system and avoid declaring python a
prerequisite for python.
Yes, I think so too.
If a package "requires" another spkg, I assume it only gets built
after the the requirement has successfully built. In that case, any
package that wants to use python during build time just has python as
a requirement. I'd expect that python can be one of the first things
that gets built anyway.
Currently the python built in Sage requires zlib, termcap, sqlite, libpng etc
all to be built first, so it's not quite as easy as that.
A sensible strategy might be:
1) Check if there is python on the system. If there is no python, go to stage 2.
If there is a usable pyton, go to stage 3.
2) Build a very basic python, without any extra libraries.
3) Build zlib, termcap sqlite, libpng etc.
4) Build a more complete python.
That avoids python being a perquisite. It just seems wrong to me to make a
package a perquisite, whilst shipping the sources for that package. Personally
though, if one is only testing if a file exists or not, a /bin/sh script would
incur less overhead.
(I'be made the assumption that you don't actually need zlib, sqlite etc to
create a basic pyton. That might not be true in the case of zlib).
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
To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or
reply to this email with the words "REMOVE ME" as the subject.
