#21674 closed enhancement (fixed)

gpgme-2.0.0, gpgmepp-2.0.0 (new)

Reported by: Bruce Dubbs Owned by: Bruce Dubbs
Priority: normal Milestone: 12.4
Component: BOOK Version: git
Severity: medium Keywords:
Cc:

Description

New major version.

Change History (18)

comment:1 by martyj19, 16 months ago

Summary: gpgme-2.0.0 → gpgme-2.0.0, gpgmepp-2.0.0 (new), qgpgme-2.0.0 (new)

The package is split into three parts: gpgme (core), gpgmepp (C++ binding), qgpgme (Qt binding). There are some API deprecation removals that might lead to build failures.

comment:2 by Xi Ruoyao, 16 months ago

gpgmepy is also separated thus the instructions regarding Python needs to be removed. I don't know if we need to add gpgmepy into Python modules/dependencies.

Last edited 16 months ago by Xi Ruoyao (previous) (diff)

comment:3 by Xi Ruoyao, 16 months ago

seahorse needs a sed:

sed '/GPGME_EVENT_NEXT_TRUSTITEM/d' -i pgp/seahorse-gpgme.c

in reply to:  3 comment:4 by Xi Ruoyao, 16 months ago

Replying to Xi Ruoyao:

seahorse needs a sed:

sed '/GPGME_EVENT_NEXT_TRUSTITEM/d' -i pgp/seahorse-gpgme.c

Upstream attempt: ​https://gitlab.gnome.org/GNOME/seahorse/-/merge_requests/248

comment:5 by Douglas R. Reno, 16 months ago

Owner: changed from blfs-book to Douglas R. Reno
Status: new → assigned

comment:6 by Douglas R. Reno, 16 months ago

This one might be a little tricky. The following packages are documented as using gpgme:

  • libreoffice
  • balsa
  • mutt
  • samba
  • KDE Frameworks
  • Seahorse
  • Mercurial
  • gmime3
  • poppler

If I'm going to have to build Mercurial I might take the opportunity to update it at the same time.

comment:7 by Douglas R. Reno, 16 months ago

I was thinking of setting up a page similar to Gedit, what are your thoughts on that? I could also break them into separate pages if desired but I feel like a combined page would be cleaner - though at the same time it might break jhalfs which isn't something I want to do

in reply to:  7 ; comment:8 by Bruce Dubbs, 16 months ago

Replying to Douglas R. Reno:

I was thinking of setting up a page similar to Gedit, what are your thoughts on that? I could also break them into separate pages if desired but I feel like a combined page would be cleaner - though at the same time it might break jhalfs which isn't something I want to do

Either way it is going to require a change to currency. I prefer a single page because I think most users will want to build all the subprojects.

in reply to:  8 comment:9 by Xi Ruoyao, 16 months ago

Replying to Bruce Dubbs:

Replying to Douglas R. Reno:

I was thinking of setting up a page similar to Gedit, what are your thoughts on that? I could also break them into separate pages if desired but I feel like a combined page would be cleaner - though at the same time it might break jhalfs which isn't something I want to do

Either way it is going to require a change to currency. I prefer a single page because I think most users will want to build all the subprojects.

But I don't even build Qt those days... And I don't think anything in the book uses qgpgme (otherwise we'd already have Qt as recommended instead of optional in the gpgme page). Maybe better just have gpgme and gpgmepp in a page.

Last edited 16 months ago by Xi Ruoyao (previous) (diff)

comment:10 by martyj19, 16 months ago

Arch is an excellent source for dependency information and they already have a split package. We can see from this list that qgpgme will probably be needed just for KDE.

​https://archlinux.org/packages/core/x86_64/qgpgme-qt6/

in reply to:  10 comment:11 by Xi Ruoyao, 16 months ago

Replying to martyj19:

Arch is an excellent source for dependency information and they already have a split package. We can see from this list that qgpgme will probably be needed just for KDE.

​https://archlinux.org/packages/core/x86_64/qgpgme-qt6/

I just "grep -r" those packages in the blfs tree and the only matches are in the archive/ directory. Thus to me we can just omit qgpgme.

comment:12 by Bruce Dubbs, 16 months ago

Milestone: 12.4 → 99-Waiting
Summary: gpgme-2.0.0, gpgmepp-2.0.0 (new), qgpgme-2.0.0 (new) → gpgme-2.0.0, gpgmepp-2.0.0 (new), qgpgme-2.0.0 (new) (API change. Wait until something needs it.)

The API change is not compatible with packages using GPGME-1.24.3. Let's wait until something needs this version.

in reply to:  12 comment:13 by Xi Ruoyao, 16 months ago

Replying to Bruce Dubbs:

The API change is not compatible with packages using GPGME-1.24.3. Let's wait until something needs this version.

The situation is different than SDL 2 vs 3 or libpeas 1 vs 2. Here the packages can use GPGME-2 but some of them needs to be adapted.

Thus I don't think we'd treat this like SDL 2 vs 3.

comment:14 by Xi Ruoyao, 16 months ago

For e.g. poppler already works with GPGME-2. But for backward compatibility it'll support both GPGME-1 and GPGME-2 for a long time (as you cannot install both of the GPGMEs w/o conflict like SDL 2 and 3). Thus if we wait we'd wait forever.

comment:15 by Xi Ruoyao, 15 months ago

Milestone: 99-Waiting → 12.4
Summary: gpgme-2.0.0, gpgmepp-2.0.0 (new), qgpgme-2.0.0 (new) (API change. Wait until something needs it.) → gpgme-2.0.0, gpgmepp-2.0.0 (new)

Bring it back and kick out qgpgme for now.

comment:16 by Bruce Dubbs, 15 months ago

Owner: changed from Douglas R. Reno to blfs-book
Status: assigned → new

comment:17 by Bruce Dubbs, 15 months ago

Owner: changed from blfs-book to Bruce Dubbs
Status: new → assigned

comment:18 by Bruce Dubbs, 15 months ago

Resolution: → fixed
Status: assigned → closed

Fixed at commits

2b2291b2a8 Update to gmime-3.2.15.
f1a258b5d3 Remove reference to gpg in mecurial test discussion.
6785a2c79d Update to gpgme-2.0.0. Add new page, gpgmepp-2.0.0.
2c420319a2 Use the updated gpgmepp dependency for kf6/kwallet.
Note: See TracTickets for help on using tickets.