kgpg is the only component which requeres build of akonadi when USE flags set to "-pim". I believe kgpg should belong to pim-related metapackage but not to generic kdeutils-meta.
Our meta packages correspond to upstream categorisation, and kgpg is in kdeutils.
Then I would make kgpg inclusion to kdeutils dependent on "pim" or "gpg" USE flag. For now I workarounded by including "kde-apps/kgpg-18.12.3-r1" to package.provided
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=6b8b6174e9c8a35bccbf3f726948c0a876d2e844 commit 6b8b6174e9c8a35bccbf3f726948c0a876d2e844 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2019-07-14 08:12:49 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-07-14 08:12:49 +0000 kde-apps/kdeutils-meta: Add USE gpg Closes: https://bugs.gentoo.org/689212 Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> kde-apps/kdeutils-meta/kdeutils-meta-19.04.3.ebuild | 4 ++-- kde-apps/kdeutils-meta/kdeutils-meta-9999.ebuild | 4 ++-- kde-apps/kdeutils-meta/metadata.xml | 1 + 3 files changed, 5 insertions(+), 4 deletions(-)