On Thursday 09 February 2012, Mike Hansen wrote: > On Thu, Feb 9, 2012 at 11:30 AM, Michael Orlitzky <mich...@orlitzky.com> wrote: > > No one has proposed anything un-vague yet. But yes, some of the > > environment variables would become ./configure options. Many of them > > would just go away though, since they manually tell the build process > > things that ./configure can determine on its own. > > This would probably also involve changing how the spkgs are built > since typically autotools will process a .in file to replace > constants. So, such a change would probably involve moving all of the > spkg-install (etc.) files out of the spkg files so that autotools can > process them. I think that change on its one might be more > worthwhile.
How about the configure script would write a makefile which would setup the right environment variables that the spkg-install scripts expect, so from their perspective nothing would change for now. > > --Mike Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: martinralbre...@jabber.ccc.de -- 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
