public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE-flag gnome-keyring isn't accurate anymore
Date: Sun, 14 May 2023 17:21:48 +0200	[thread overview]
Message-ID: <5949454.lOV4Wx5bFT@tuxbrain> (raw)
In-Reply-To: <CAMtWw9w4D4uqRF5N7ASc9N_qgdoP2Zz--Tt9FYJT4-+94A4C0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Sonntag, 26. Dezember 2021 11:10:45 CEST John Johnson wrote:
> On Sat, Dec 25, 2021, 5:19 AM Marek Szuba <marecki@gentoo.org> wrote:
> > On 24 December 2021 08:48:08 UTC, Pacho Ramos <pacho@gentoo.org> wrote:
> > >> > I think “secret” may be too generic and “libsecret” is not ideal in
> > >> > case an implemention comes along that is named differently. How about
> > >> > “secret-service”?
> > >> 
> > >> I think this is a good idea.
> > >
> > >And "keyring"? I am not sure if users not familiar with "libsecret" will
> > >understand what "secret*" means in this context
> > 
> > Definitely a good idea. And I second "keyring", seeing as this term is
> > also in use on other OSes.
> > 
> > --
> > Marecki
> 
> "keyring" conveys the appropriate meaning, imho.
> 

It seems that keyring won the popular vote. There is now a bug and a PR:

https://bugs.gentoo.org/905928
https://github.com/gentoo/gentoo/pull/31035

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 789 bytes --]

      reply	other threads:[~2023-05-14 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 21:35 [gentoo-dev] USE-flag gnome-keyring isn't accurate anymore tastytea
2021-12-23 22:46 ` Matt Turner
2021-12-24  8:48   ` Pacho Ramos
2021-12-25 11:18     ` Marek Szuba
2021-12-25 11:18     ` Marek Szuba
2021-12-26 10:10       ` John Johnson
2023-05-14 15:21         ` Andreas Sturmlechner [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=5949454.lOV4Wx5bFT@tuxbrain \
    --to=asturm@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