From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] configure: use pkg-config for gpgme
Date: Fri, 11 Nov 2022 05:16:31 -0500 [thread overview]
Message-ID: <87edu97q4g.fsf@fifthhorseman.net> (raw)
In-Reply-To: <878rktvznb.fsf@tethera.net>
[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]
On Wed 2022-11-02 18:02:00 -0300, David Bremner wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>> GnuPG upstream has supported pkg-config since gpgme version 1.13 and
>> gpg-error 1.33, and now prefers the use of pkg-config by default,
>> instead of relying on gpg-error-config and gpgme-config.
>>
>> As of libgpg-error 1.46, upstream deliberately does not ship
>> gpg-error-config by default. As of gpgme 1.18.0, upstream does not
>> ship gpgme-config if gpg-error-config is also not present.
>>
>> Both of these versions of upstream libraries are in debian unstable
>> now. To the extent that notmuch is dependent on GnuPG, it should
>> follow GnuPG upstream's lead.
>
> How is the (debian specific) story for backports?
I believe this patch leaves notmuch still fully backportable across
all supported debian versions that were already supported.
0 dkg@alice:~$ rmadison gpgme1.0
gpgme1.0 | 1.5.1-6 | oldoldoldstable | source
gpgme1.0 | 1.8.0-3 | oldoldstable | source
gpgme1.0 | 1.12.0-6~bpo9+1 | stretch-backports | source
gpgme1.0 | 1.12.0-6~bpo9+1 | stretch-backports-debug | source
gpgme1.0 | 1.12.0-6 | oldstable | source
gpgme1.0 | 1.14.0-1 | stable | source
gpgme1.0 | 1.18.0-1 | testing | source
gpgme1.0 | 1.18.0-2 | unstable | source
gpgme1.0 | 1.18.0-2 | unstable-debug | source
0 dkg@alice:~$
backporting to stable should use pkg-config, since the version there is
after 1.13. for older than stable, the functionality will still fall
back to using legacy gpgme-config.
--dkg
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-11-11 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:15 [PATCH] configure: use pkg-config for gpgme Daniel Kahn Gillmor
2022-11-02 21:02 ` David Bremner
2022-11-11 10:16 ` Daniel Kahn Gillmor [this message]
2023-01-09 18:19 ` Daniel Kahn Gillmor
2023-01-10 12:45 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edu97q4g.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).