Le 8/2/2012, Keshav Kini <keshav.k...@gmail.com> a écrit : > Upstream configure scripts tend to check for dependencies by just > testing if it can use them. I guess what is meant here is that > spkg-install could check whether certain SPKGs had been installed > into the Sage installation. Also, upstream might not be aware of > certain dependencies it might gain by whatever patches we apply to it > (though we could patch the upstream configure script, I guess...).
Wouldn't it be wiser if instead of checking that kind of dependency with spkg-install, the spkg could contain a "deps" file in which "sage -i" could have a look, and decide to install said dependencies before actually running spkg-install at all? Snark on #sagemath -- 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
