[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#37556: gpg "-unknown" version string
|
From: |
Kazuhiro Ito |
|
Subject: |
bug#37556: gpg "-unknown" version string |
|
Date: |
Tue, 01 Oct 2019 23:59:20 +0900 |
|
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/27.0 (x86_64-w64-mingw32) MULE/6.0 (HANACHIRUSATO) |
> >>> I don't understand why making -unknown equivalent to a lesser version
> >>> makes sense. Shouldn't 2.2.17 and 2.2.17-unknown in fact be equal?
> >>
> >> Should they? 2.2.17-pre and 2.2.17-alpha should be less than 2.2.17,
> >> but how do we know that -unknown isn't something -alpha-ish?
> >
> > It's "unknown", so it could be something opposite-of-alpha-ish too,
> > right? On average, 0 seems right.
>
> That's possible. Does anybody know how usual these -unknown things are,
> and why they exist?
I don't know "why", but I described when the suffix was added in the
past post.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35629#11
> GnuPG's autogen.sh makes "-unknown" suffix version configure script if
> source code directory doesn't have .git directory.
If you have the repository, autogen.sh can set an apropriate revision
number. I guess "-unknown" version means "unknown version" literally,
because they couldn't decide the source code revision without
repository.
--
Kazuhiro Ito