From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] global USE=gpg
Date: Sun, 7 Jan 2024 23:46:14 +0100 [thread overview]
Message-ID: <f006f786-74cc-499f-ad52-c9165dbd74c8@gentoo.org> (raw)
In-Reply-To: <3547018.aeNJFYEL58@noumea>
[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]
>>> 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.
>
> Yeah, typical case of "formally correct thing being way more difficult to
> understand than colloquially practical thing" ...
You are right.
I would prefer the formally correct "OpenPGP" after reading a bit more.
This is how it is named in the RFCs [1] and this is what we mean.
If we use either gpg or pgp it will raise new questions and confuse the
users.
It is better to write 4 additional characters and make it simple and
precise.
We can explain all details in the description then.
[1] https://datatracker.ietf.org/doc/html/rfc4880
--
Best,
Jonas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-01-07 22:46 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
2024-01-07 22:46 ` Jonas Stein [this message]
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=f006f786-74cc-499f-ad52-c9165dbd74c8@gentoo.org \
--to=jstein@gentoo.org \
--cc=gentoo-dev@lists.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