Hi! I've noticed that the gnome-keyring use-flag is not accurate
anymore for most packages. The only ebuilds with that flag that depend
on gnome-base/gnome-keyring seem to be[1] sys-auth/pambase and mate-base/mate-session-manager.
All others depend on app-crypt/libsecret, which depends on virtual/secret-service.
virtual/secret-service currently depends on gnome-base/gnome-keyring or app-admin/keepassxc and KSecretService will be added too once upstream
is ready.
That's confusing for users of a secret service provider other than gnome-keyring, so I propose we find a new use-flag.
x11-plugins/wmudmount already uses “secret” and mate-extra/mate-power-manager uses “libsecret”.
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”?
Previously discussed in <
https://bugs.gentoo.org/829730>.
Kind regards, tastytea
[1] I did a rather naive search with
`grep -Er 'gnome-keyring\?.*gnome-keyring' \
$(portageq get_repo_path / gentoo)`
--
Get my PGP key with `gpg --locate-keys
[email protected]` or at <
https://tastytea.de/tastytea.asc>.
-----BEGIN PGP SIGNATURE-----
iHUEAREKAB0WIQQ1VSZoZMptf/RapufPw5SX8bJuBwUCYcTrhAAKCRDPw5SX8bJu B/KiAP0aBlrP1jGxGi2AxNYwJDKrAMUUV/1Z2jf017Qt1Dho/gD/c4LOVkp0M7aN 9PpA6+zuvXusgmOV58AqGgI2CYfNii8=
=qpMD
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)