Also, a top-level configure script is the natural point to select alternatives to 3rd party code. For example, one should be able to
./configure --with-mpir=/usr --with-gap=/usr/local to use an external mpir and gap install... On Thursday, April 11, 2013 8:00:30 AM UTC+1, Jeroen Demeyer wrote: > > On 04/11/2013 01:53 AM, R. Andrew Ohana wrote: > > For those so inclined to browse the current status of the git > > transition, the repository is at https://github.com/sagemath/sage. > Yes, it is completely obvious that this Debian packaging effort should > start from the GIT repository, not from the current way Sage is > distributed. > > Concerning a top-level configure script: having such a script is > something I'm already planning anyway. So, yes, we should absolutely > have a top-level configure script. Almost all of the stuff currently in > spkg/base/prereq* and spkg/install should move there, and then these > files should be removed. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
