Restructuring the automake and autoconf packages
Sun Dec 2 15:21:00 GMT 2001
I have a couple of questions regarding this (apologies
if already covered - I'm on the digest and only got
this message on announce).
Let's see if I understand correctly:
1. you run autoconf
2. it sets the path based on a wrapper script
3. next execution goes to the desired one directly.
Doesn't this limit you to only running ./configure for
one package within a single bash shell? (or removing
the env. variable/modifying PATH). It sounds like a
good idea for effeciency, but I'm a bit worried about
the confusion factor.
Also, I think you stated the default is autoconf-2.52.
This seems to be back to front as many old
configure.in's might not AC_PREREQ(2.13), whereas
newer ones are probably inclined to AC_PREREQ(2.52)
since the uptake is lower. I'm not sure I'm right on
this, really everyone should request what they want
anyway, but its food for thought.
Good work on this - I think it's a great solution to
the problem for now. A better libtool is worth it.
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
More information about the Cygwin