[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf-2.69c released [beta]
From: |
Bruno Haible |
Subject: |
Re: autoconf-2.69c released [beta] |
Date: |
Sun, 27 Sep 2020 23:55:18 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-189-generic; KDE/5.18.0; x86_64; ; ) |
[CCing Autoconf list again]
Paul Eggert wrote:
> I am assuming that "m4_version_prereq([2.69.301-14265], ...)" does the right
> thing with Autoconf beta version numbers; if not, that's an Autoconf bug that
> should get fixed....
Well, I don't know where you got this magic number 301-14265 from.
In my tests with version 2.69c,
m4_version_prereq([2.70], NEW, OLD)
picked the OLD code, whereas
m4_version_prereq([2.69c], NEW, OLD)
picked the NEW code.
The version comparison code (see m4sugar.m4, macro m4_version_unletter) seems
to handle prerelease version numbers fine.
In a git checkout of the Autoconf repository, when I run
build-aux/git-version-gen .tarball-version
it prints
2.69c.2-04d14
As far as I can see, versions of the form 2.69.xx-yyy will all be considered
smaller than even the first prerelease (2.69a); so that's probably not a
desirable way to designate intermediate versions between 2.69b and 2.69d.
Bruno
- Re: autoconf-2.69c released [beta], (continued)
- Re: autoconf-2.69c released [beta], Gavin Smith, 2020/09/27
- Re: autoconf-2.69c released [beta], Bob Friesenhahn, 2020/09/27
- Re: autoconf-2.69c released [beta], Gavin Smith, 2020/09/27
- Re: autoconf-2.69c released [beta], Gavin Smith, 2020/09/27
- Re: autoconf-2.69c released [beta], Bob Friesenhahn, 2020/09/29
- Re: autoconf-2.69c released [beta], Russ Allbery, 2020/09/29
- Re: autoconf-2.69c released [beta], Zack Weinberg, 2020/09/30
Re: autoconf-2.69c released [beta], Zack Weinberg, 2020/09/30
Message not available