On 26 Okt., 12:39, Volker Braun <vbraun.n...@gmail.com> wrote: > 2) a "configure"-like test script that tests the requirements and > gives useful hints on how to install missing pieces of the toolchain > and/or required libraries.
Yep. Especially odd is that Sage ships four MacOS X *binaries* in a so- called *source* distribution. (The Linux binaries were removed a while ago.) One could consider the bunch of fonts shipped also binaries, i.e. these should IMHO be moved to separate packages, since they don't change that frequently, at least not as often as the packages that currently contain them. (Some of these and even obsolete ones are in the package's Mercurial repository, too, btw.) I'd also prefer a concept of platform-specific spkgs (perhaps also tarballs specific to e.g. Darwin and Cygwin), cf. http://groups.google.com/group/sage-release/msg/6564b50668274ae7 -Leif -- 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
