[pkg-gnupg-maint] A merge request to libgpg-error

[Daniel Kahn Gillmor]

Hi gniibe--

On Tue 2023-08-08 17:06:01 +0900, NIIBE Yutaka wrote:

> I confirmed that it *is* fragile, indeed.  So, it is easily risky.
> Andreas Metzler is right.

thanks for your work looking into this -- i want to echo Andreas's
observation that it didn't come across as violent or disruptive at all.
You see a problem you're trying to solve; you offered some solutions,
and then you rolled them back when you saw an unfavorable outcome.  It's
all good!

As for how to name the library files for windows: the stuff that Debian
builds is explicitly intended to be used for dll's for Debian installers
like the one found at https://www.goodbye-microsoft.com/ or the
win32-loader component of debian-installer (see "apt show win32-loader")
-- so the choice of filename isn't particularly important, as long as
the applications which use it (e.g. gpgv.exe from the gpgv-win32
package, in this case) know what they're looking for.

for 64-bit Windows, I don't know whether anyone is working on a
"win64-loader" or equivalent at all.

I don't think it was ever intended (certainly not by me) for these
generated versions of Windows libraries to be installed for regular
cross-application use on a normal Windows system, and i wouldn't want
them to be seen as replacements for any upstream official builds of the
associated libraries.

Does that affect how you think about the library naming schemes?

I don't fully understand the sed script approach you're describing, or
how it fits into the larger picture of building the OS installer, but
i'd be happy to review if you think that would be useful.

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