On Tue, 2004-09-07 at 11:59, Andrew Dougherty wrote: > Both autoconf and metaconfig assume a unix-like environment. Ambitious > plans for parrot's configure include non-unix environments too, such as > VMS and all the ports where perl5 uses a manually-generated config.* > template.
autoconf assumes m4 and shell and some other primitive tools, all of which have GNU ports to just about everything I've had to touch. VMS is the bastard child of autoconf right now, but back when VMS was a platform that folks used, it certainly was supported (as late as 1999 it worked great). I don't think it's the UNIXishness of the platform as much as the popularity of the platform that guides autoconf support (e.g. any platform for which patches are contributed). The guy who tried to update the autoconf 1.x version this year kind of kicked the autoconf guys in the shins verbally and got nowhere as a result. He then forked it and has since apparently dropped support. That said, if you have a manually generated template as you do for Perl 5, you can do the same for autoconf, no? I'm not advocating autoconf here, just exploring the lay of the land. Personally, I think Parrot should do whatever makes it easiest for maintainers. -- â 781-324-3772 â [EMAIL PROTECTED] â http://www.ajs.com/~ajs
