Drop 'unknown' suffix in runtime version
Yi Zhao
yi.zhao at windriver.com
Tue May 27 04:43:18 CEST 2025
On 5/19/25 23:06, Ingo Klöcker wrote:
> On Sonntag, 18. Mai 2025 10:57:33 Mitteleuropäische Sommerzeit Yi Zhao via
> Gnupg-devel wrote:
>> When I build gunpg in Yocto, a "-unknown" suffix appears in the gpg
>> runtime version:
>>
>> $ gpg --version
>> gpg (GnuPG) 2.5.5-unknown
>>
>> This is because the configure will be re-generated by autoreconf in
>> Yocto. The autogen.sh will add "-unknown" suffix to PACKAGE_VERSION.
>> Now I have a simple patch to remove this suffix in autogen.sh.
>> I wonder if there is a more appropriate way to resolve this? Thanks.
> Some Linux distributions have similar patches to remove this suffix because for
> some reason or other they also regenerate the configure script. Since the Linux
> distributions also apply other patches it's actually not nice that they remove
> the suffix because they clearly don't ship the version that their packages
> announce. If they don't like the "-unknown" suffix then they should append a
> suffix like "-DISTRONAME" so that everybody knows that they don't use the
> released version as-is.
>
> If you use the released version without any other patches then using a patch
> that just removes the "-suffix" is okay.
Thanks for your response. May I know why gnupg adds this suffix? As far
as I know, it is not uncommon to re-run autoreconf on the tarball.
And I found that other gnupg-related packages such as libksba,
libassuan, libgcrypt, pinentry, libgpg-error also add this suffix.
//Yi
>
> Regards,
> Ingo
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-devel
More information about the Gnupg-devel
mailing list