The "gpg" use-flag is used by lots of packages: # q use -D gpg local:gpg:app-backup/dar: Enables usage of asymetric crypto algorithms local:gpg:app-crypt/qca: Enable GnuPG plugin local:gpg:app-portage/gemato: Install dependencies needed for OpenPGP signature verification support local:gpg:app-portage/layman: Support app-crypt/gnupg signed overlays lists and manifests local:gpg:dev-util/diffoscope: Use app-crypt/gnupg local:gpg:dev-util/geany-plugins: Enable geanypg plugin which integrates GPG using app-crypt/gpgme local:gpg:dev-vcs/git: Pull in gnupg for signing -- without gnupg, attempts at signing will fail at runtime! local:gpg:dev-vcs/mercurial: Support signing with GnuPG. local:gpg:kde-apps/kget: Enable signature verification by GpgME++ via app-crypt/gpgme local:gpg:kde-frameworks/kwallet: Support wallets with GnuPG encryption in addition to the default blowfish-encrypted file local:gpg:mail-client/mutt: Enable support for app-crypt/gpgme local:gpg:mail-client/neomutt: Enable support for app-crypt/gpgme local:gpg:net-firewall/fwknop: Enable GPG support via app-crypt/gpgme local:gpg:net-fs/samba: Use app-crypt/gpgme for AD DC local:gpg:net-im/ekg2: Enable jabber message encryption through app-crypt/gpgme. local:gpg:net-nntp/tin: Enable app-crypt/gnupg support local:gpg:sys-apps/fwupd: Enable GPG support. local:gpg:sys-apps/pacman: Enable GPG signature verification using app-crypt/gpgme local:gpg:sys-fs/ecryptfs-utils: Enable app-crypt/gnupg key module local:gpg:sys-kernel/genkernel-next: Enable support for GPG (include gnupg dependency) On the other hand IUSE=gnupg is much more seldom: # q use -D gnupg local:gnupg:app-admin/salt: Enable support for gnupg via python-gnupg. local:gnupg:net-im/dino: Enable OpenPGP encryption plugin I suggest to change app-admin/salt to use IUSE=gpg instead.
