8000 [WIP] gpgme 2.0 porting by johu · Pull Request #1048 · gentoo/kde · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[WIP] gpgme 2.0 porting #1048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[WIP] gpgme 2.0 porting #1048

wants to merge 1 commit into from

Conversation

johu
Copy link
Contributor
@johu johu commented Jun 16, 2025

No description provided.

This version bump is a proxy to app-crypt/gpgme-1.4.3[cpp] to facilitate
the porting of the reverse dependencies to version 2.0.0.

With version >=2.0.0 the language bindings for C++, Qt and Python of
app-crypt/gpgme are split into separate packages (namely
dev-cpp/gpgmepp, dev-libs/qgpgme and dev-python/gpgmepy).

Signed-off-by: Johannes Huber <johu@gmx.de>
@johu johu force-pushed the gpgme-porting-aid branch from 26afde5 to 4a8ce34 Compare June 16, 2025 19:00
HOMEPAGE="https://www.gnupg.org/related_software/gpgme"

# keep license, slot and keywords in sync with app-crypt/gpgme
LICENSE="GPL-2 LGPL-2.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make it a metapackage [LICENSE]. media-sound/pulseaudio is a precedent, with the difference that it fully replaced the old "real" package and solely diverted to split packages.

Comment on lines +14 to +17
DEPEND="
~app-crypt/gpgme-${PV}:=[cxx]
"
RDEPEND="${DEPEND}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

metapackages only have RDEPEND, no DEPEND, so it can be as simple as a oneliner.

However - what does the slot operator here really achieve? You're already (correctly) limiting to ~${PV}, so it is highly unlikely the := slot op will ever trigger. Even if in theory e.g. packaging needs would require us to bump app-crypt/gpgme-1.24.3's subslot in a revbump - what would happen? Just a pointless rebuild of this metapackage without that being relayed to revdeps that would actually need it. Consequently, SLOT must align with the one from app-crypt/gpgme-${PV}, and RDEPEND must pin down to that slot as well:

Suggested change
DEPEND="
~app-crypt/gpgme-${PV}:=[cxx]
"
RDEPEND="${DEPEND}"
RDEPEND="~app-crypt/gpgme-${PV}:${SLOT}[cxx]"

This will be annoying should there ever be another gpgme-1.x.x version bump, since it requires bumping all related metapackages. But we don't expect any, or at least just plan to move to gpgme-2 fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0