On Thursday, August 9, 2012 2:43:22 PM UTC+2, Jeroen Demeyer wrote: > > autotools is absolutely something to be used at packaging-time, not > build-time. > > To solve most of the problems in this thread, I am preparing an > experimental autotools spkg containing the latest m4 and many versions > of autoconf, automake and libtool. > I'm a little bit confused.
You first say it's a bad idea to use autotools at build-time (which I a'gree with, but that's not relevant). And then that you are crafting an autotools spkg, which as I understand implies that you suggest to use it at build-time. Maybe only as temporary solution then, while waiting for upstream packaging, and to avoid killing the hg history? In this scenario, what about spkg for which upstream basically does not exist anymore ? Should we run autotools in the spkg as long as the spkg exist? Or in this specific case, which hopefully will be rare, should we do something else? Like directly patching the src dir, regenerating the autotools machinery, and providing a separate "already-applied-patches-directory" where the patches to the .am and .ac files only would reside and be tracked (and maybe some indication of what autotools version were used for the regeneration)? -- -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
