[pkg-gnupg-maint] Bug#1071202: Bug#1071202: src:gnupg2: upstream tarball ships files not in upstream revision control

[Daniel Kahn Gillmor]

Hi gniibe--

Thanks for this additional info!

On Fri 2024-05-17 09:02:40 +0900, NIIBE Yutaka wrote:
> The regexp subdirectory was introduced to support POSIX regexp functions
> on Windows.  The intention is providing same behavior among GnuPG on
> different Operating Systems.  Historically, regexp in OpenPGP had been
> not supported by Windows versions of GnuPG; In the past, when a user
> switched his Operating System from common POSIX one to Windows, it
> stopped working.
>
> If it is only for Debian, possibly, we can simply use POSIX regexp
> functions in the C library, perhaps.

If GnuPG doesn't use this regexp dir when building on Debian, that
sounds fine to me :)  Then we definitely don't need to use or ship that
mapping file!  

> There are corner cases for regexp matching among different regexp
> functions support and Unicode versions.

yes, the regexp support in the standard is ill-specified in a lot of
ways, and most implementations struggle to implement it properly, for
all kinds of reasons.

We don't have good interop tests for it yet because we haven't extended
sop into certificate management.  I should probably try to get that
under way. :/

> Strictly speaking about a data specification, it would be more acculate
> to specify exact Unicode version explicitly in the OpenPGP standard.

Unicode is supposed to evolve in a stable and sane way.  I think tying
OpenPGP to a specific version of Unicode would be a mistake; it's hard
enough to upgrade OpenPGP as it is, without having to coordinate across
versions of unicode in the first place.

         --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 324 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20240520/d80b4aa7/attachment.sig>