Am 29.08.2014 um 20:04 schrieb Bob Friesenhahn <[email protected]>:
> All of these strategies are done in m4 and result in the configure script
> being re-generated, which seems senseless and annoying to me. I will do
> anything in my power to not modify what has already been exhaustively tested
> just seconds before a release. The new configure script might not even work
> or it may behave differently than before.
>
> I see hardly any relationship between the configure script and the release
> versioning other than that the configure script prints it for the user and
> records the value.
>
> The logic of the configure script does not depend on the version values (they
> are just passed strings) so it was a design error to require that the user
> edit configure.ac (or some m4 file) in order to cut a new release.
Fwiw, Netatalk sources a file containing the version info:
$ cat VERSION
3.1.7dev$
configure.ac:
NETATALK_VERSION=`cat $srcdir/VERSION`
AC_SUBST(NETATALK_VERSION)
AM_INIT_AUTOMAKE(netatalk, ${NETATALK_VERSION})
Cheerio!
-f
_______________________________________________
Autoconf mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/autoconf
