On 8/22/24 11:38 AM, ralfconn wrote:
> Il 22/08/24 06:50, Eli Schwartz ha scritto:
>>
>> emerging portage itself, will require gnupg as a dependency, and in
>> turn that means app-crypt/pinentry If pinentry is built with
>> USE=keyring, it requires app-crypt/libsecret, which in turn has a
>> PDEPEND for virtual/secret-service, so that you can actually have
>> something implementing a keyring. There are exactly two current
>> implementations of a secret-service API provider: - gnome-keyring -
>> keepassxc And that is how keepassxc comes to be a "dependency" of the
>> @system set. Due to optional USE flags. :)
>
> That makes sense, thanks (wow, it is complicated!)but there must be
> something else because here:
>
> - pinentry does not USE keyring:
> # eix -I pinentry [I] app-crypt/pinentry Available versions: 1.2.1-r7
> (~)1.2.1-r8 (~)1.3.0-r3 (~)1.3.1 {X caps efl emacs gtk keyring ncurses
> qt5 qt6 verify-sig wayland} Installed versions: 1.3.1(16:25:28
> 07/06/24)(X gtk ncurses qt5 -caps -efl -emacs -keyring -qt6 -verify-sig
> -wayland)Dunno then. You can try emerge -cpv keepassxc app-crypt/libsecret virtual/secret-service and trace the reported blockers yourself if you're really curious. :D > - portage is not in @system: Ah, but virtual/package-manager *is* in @system, and depends on your choice of portage or pkgcore but in practice always portage... -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
