[pkg-gnupg-maint] Bug#1073255: Qt 6 bindings for gpgme
Andreas Metzler
ametzler at bebt.de
Sun Jun 16 17:35:03 BST 2024
On 2024-06-16 Andreas Metzler <ametzler at bebt.de> wrote:
> On 2024-06-15 Patrick Franz <deltaone at debian.org> wrote:
[...]
>> Currently, gpgme offers Qt 5 bindings, but for Plasma 6 we will need the
>> Qt 6 bindings for gpgme. Is it possible to add them ?
> 1.19.0 added "Optionally, build QGpgME for Qt 6". Which
> afaict gives the same header files but a soname of libqgpgmeqt6.so.15
> instead of libqgpgme.so.15.
Hello,
I have packaged 1.23.2 (TODO: debian/copyright update) and have added a
first draft of packaging QT 6 bindings.
https://salsa.debian.org/debian/gpgme/-/commits/tmp-ametz-debian%2Fexperimental?ref_type=heads
(There is a corresponding also ff-able tmp-ametz-upstream branch.)
I started with splitting of the QT5 parts as libqgpgme-dev from
libgpgme-dev (unfuzzed patch by Rene Engelhard on #863149) and added
libqgpgmeqt6-15 / libqgpgmeqt6-dev. This requires building gpgme twice
in a row since qt5 and qt6 cannot be enabled together.
I have chosen to use separate, conflicting qt5/qt6 development packages.
This is the ultra-conservative approach but I am not sure it is the
best/right one. Currently all common files in the two dev-packages are
bit-for-bit identical (/usr/include) so it would be possible to merge
these now. I just do not know whether they will stay that way. I will also
ask upstream.
cu Andreas
More information about the pkg-gnupg-maint
mailing list