public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>,
	"Andreas K. Huettel" <dilfridge@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] global USE=gpg
Date: Sun, 31 Dec 2023 12:27:41 +0100	[thread overview]
Message-ID: <17a56f1b-f4aa-47d8-9db0-287f4234f184@gentoo.org> (raw)
In-Reply-To: <3547018.aeNJFYEL58@noumea>


[-- Attachment #1.1.1: Type: text/plain, Size: 922 bytes --]

On 30/12/2023 16.54, Andreas K. Huettel wrote:
>>> we have many local gpg useflags which basically just enable gpg.
>>> Should we merge these to one global useflag?
>>>
>>> Additionally we have a few gpgme useflags.
>>> See also https://bugs.gentoo.org/679634
>>>
>>> What are your ideas?
>>>
>>
>> We have also have a bunch of USE=pgp and USE=openpgp, both of which are
>> more correct than USE=gpg.

I am always confused when people use "gpg" to talk about OpenPGP.


> Yeah, typical case of "formally correct thing being way more difficult to
> understand than colloquially practical thing" ...

It is only a matter of time until the more users of gnupg-alternative 
libraries, like sequoia or librnp, appear. USE=gpg is probably already 
sometimes a misnomer, and will definitely be one if we make it a global 
USE flag and there are packages that declare it without pulling in gpg.

- Flow


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2023-12-31 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 23:41 [gentoo-dev] [RFC] global USE=gpg Jonas Stein
2023-12-30  5:09 ` Michał Górny
2023-12-30 15:54   ` Andreas K. Huettel
2023-12-30 16:54     ` Ulrich Mueller
2023-12-31 11:27     ` Florian Schmaus [this message]
2024-01-07 22:46     ` Jonas Stein

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17a56f1b-f4aa-47d8-9db0-287f4234f184@gentoo.org \
    --to=flow@gentoo.org \
    --cc=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox