> > Axiom as it exists now > > a) depends on very little > > b) never writes outside of its own directory (not even tmp files) > > c) builds everywhere (or tries to) > > Could you live with an axiom-built-procedure that > checks the system, if something is missing, it downloads the appropriate > files (either from their original source place or from > axiom-developer.org/prerequisites) and installs them following (b) from > above. > > The only difference to the current Axiom would be that checking and > installing prerequisites is done before the actual axiom-make starts. > And, the axiom archive will be smaller, since some people might have > already installed some software. > > You said that now Axiom (via gcl) depends on Emacs, but I guess you > don't want to include emacs into axiom--main--1, do you? (Otherwise > axiom does not "just work". ;-) )
It appears that GCL depends on some awk/sed change that somehow gets packaged with emacs (I'm guessing since I don't actually know the source but Camm has suggested that might be the problem). I'm going to find the problem and write a GCL patch so that it no longer occurs, send the patch to Camm, and put the patch in zips against the current GCL versions. That way Axiom 'just works'. Curiously the issue first arises on a debian system which is supposed to be really good at the whole dependency handling. t _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer