GNU bug report logs - #75880
relax five-digit maximum on revisions?

Previous Next

Package: libtool;

Reported by: Karl Berry <karl <at> freefriends.org>

Date: Sun, 26 Jan 2025 22:36:01 UTC

Severity: normal

Done: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Karl Berry <karl <at> freefriends.org>
To: 75880 <at> debbugs.gnu.org
Cc: luigi.scarso <at> gmail.com
Subject: bug#75880: relax five-digit maximum on revisions?
Date: Sun, 26 Jan 2025 15:35:07 -0700
Hi Ileana and all - in ltmain.in, there is:

    case $revision in
    0|[1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1-9][0-9][0-9][0-9][0-9]) ;;
    *)
      func_error "REVISION '$revision' must be a nonnegative integer"
      func_fatal_error "'$vinfo' is not valid version information"
      ;;
    esac

Which allows for at most five digits of $revision.
Is there a technical reason for that, or is it arbitrary?
Can it be increased, perhaps allowing any number?

My friend Luigi (cc-d) incorporates the luajit library into luatex with
libtool. Luajit is now a rolling release. Therefore using epoch-seconds
or similar seems reasonable, since there is no specific revision number
other than that. For example, 1736781742 (corresponding to a couple
weeks ago).

Wdyt?

Thanks,
Karl

P.S. I speculate that there's a technical maximum of 32 or 64 bits, so
"any" number (as in \d+) would technically be wrong, but presumably such
a huge number will fail at some point. IMHO the user doesn't deserve a
nice error message if they exceed a maximum like that.




This bug report was last modified 191 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.