Re: [tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-15 Thread Guy Harris
On Apr 15, 2013, at 7:18 AM, François-Xavier Le Bail wrote: >> From: Guy Harris >> If we want to ensure that the configuration scripts we ship are generated by >> a >> particular version of autoconf, we should remove configure from the >> repository, >> add an autogen.sh script to re-gener

Re: [tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-15 Thread François-Xavier Le Bail
> From: Guy Harris > If we want to ensure that the configuration scripts we ship are generated by > a > particular version of autoconf, we should remove configure from the > repository, > add an autogen.sh script to re-generate the configure file, and ensure that > it's run as part of the rel

Re: [tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-13 Thread Guy Harris
On Apr 13, 2013, at 3:01 AM, François-Xavier Le Bail wrote: > Tha last configure file is "Generated by GNU Autoconf 2.61.". > > The previous was "Generated by GNU Autoconf 2.68.". > > Is there any risks of regression ? If we want to ensure that the configuration scripts we ship are generated

Re: [tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-13 Thread Michael Richardson
> "ois-Xavier" == ois-Xavier Le Bail writes: ois-Xavier> Tha last configure file is "Generated by GNU Autoconf 2.61.". ois-Xavier> The previous was "Generated by GNU Autoconf 2.68.". ois-Xavier> Is there any risks of regression ? oh, I thought it was updating the other way when

[tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-13 Thread François-Xavier Le Bail
Hello, Tha last configure file is "Generated by GNU Autoconf 2.61.". The previous was "Generated by GNU Autoconf 2.68.". Is there any risks of regression ? Francois-Xavier ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lis