Gonzalo Tornaria wrote:
Plus, there can *still* be spkgs for all the dependencies. And there
could be a "sage-with-batteries-included" tarball which works just as
it does now. And another
"sage-reduced-for-expert-developers-and-distros" tarball which doesn't
include the spkgs which can be replaced by distro packages. Even the
prereq script could actually *check* the dependencies, and (offer to)
download the required spkg !!! (then the tarballs could be named
"sage-full-install" vs. "sage-net-install".)
IMO sage is mature enough now.
Best, Gonzalo
I was just going to say that in principle there is nothing stopping sage finding
out what it needs, then automatically downloading packages from the sage web
site. But I realised you had said it!! But yes, it could be done.
But sorting out whether the version of libraries on a system are suitable, can
be tricky. Even having the right versions does not guarantee they will be found
in preference to some other version.
I can see some advantages in not shipping basic things, but I can see that one
might need to spend a LOT of time developing the build system to do this.
If you are only going to shave off 20 MB or so from the source code, it might be
more hassle than it is worth. If you could cut the download time by 30%, then I
could see it would probably be worth the effort in doing this. But I'm not so
sure you would be able to do that. Too many packages are probably too specialised.
An obvious question is whether there would be anyone willing to take on the task
of changing this? I for one would not want to. Would anyone else ??
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
