Re: rfc: update autoconf in MAIN?

On 18/12/06, Thomas Anders <thomas.anders@blue-cable.de> wrote:
> Wes Hardaker wrote:
> > ....any reason we shouldn't push the requirement [for autoconf 2.61]
> > to all branches?
>
> It may break packaging for those who forcibly run "autoconf" when
> building (and only very few systems already ship 2.61). OTOH, it may
> make life easier for core developers. I'd propose to update MAIN first
> and see how it goes.


I've recently been running configure on both the main development
line and various branches in rapid succession, and suddenly realised
that I wasn't being prompted for the "manual settings" on the trunk
line. (i.e. default version, contact, location, etc)

Further investigation seems to indicate that this is purely down to
the switch to autoconf 2.61. Regenerating the 5.4.x configure from
configure.in using autoconf 2.61 results in exactly the same behaviour.

I haven't had a chance to track down *why* this is happening,
but it feels a bit worrying. Can anyone shed any light on this,
or offer suggestions as to how best to proceed?

Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders