On 8/22/24 12:40 AM, ralfconn wrote: > Hello, > > On my system: > emerge -p @world | wc -l > 198 > emerge -ep @world | wc -l > 1151 > emerge -p @system | wc -l > 56 > emerge -ep @system | wc -l > 502 > > The last one does not look right, in particular the list of packages > contains some from @world (e.g. keepassxc). I am running a local mixed > profile local:23.0-no-multilib-hardened-desktop which I thought could be > the culprit, but merely switching to default/linux/amd64/23.0 (without > recompiling) does not change much the numbers. The same happens on > another box where the difference between -e @world and -e @system is > even more ridiculous (~750 vs ~500). Again there I use a mixed local > profile, something like local:23.0-hardened-desktop. > > Could the mixed profile be the reason? What numbers do others have?
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. :) -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
