[tcpdump-workers] autoconf 2.61 versus 2.68
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://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] autoconf 2.61 versus 2.68
> "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 I was reading the diff. hmm. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] autoconf 2.61 versus 2.68
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 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 release-tarball building process. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
