rename gpgmeqt -> qgpgme-qt5

[Luciogi]

No description provided.

[ahesford]

Subpackage names are kind of arbitrary, and while gpgme-qt5 or something might be better, qgpgme-qt5 is just arbitrary in a different way. Package renames are also a bad experience in general.

[Luciogi]

Subpackage names are kind of arbitrary, and while gpgme-qt5 or something might be better, qgpgme-qt5 is just arbitrary in a different way. Package renames are also a bad experience in general.

shlib-provides:
        libqgpgmeqt6.so.15

qt bindings of gpgme provide above library, it makes logical to have package name qgpgme-qt6

[classabbyamp]

if that's a new (sub)package, go ahead and name it that way, but changing the existing package is not necessary

[Luciogi]

if that's a new (sub)package, go ahead and name it that way, but changing the existing package is not necessary

yes gpgmeqt is subpackage

[ahesford]

I didn't realize that the Qt5 package was nothing more than a library. We have a naming convention that should be applied to any new subpackage here. The new addition ought to be called libqgpgmeqt6{,-devel} or, because that's an illegible jumble of Q, P and G, maybe libqgpgme-qt6{,-devel}.

Still, changing the name of the existing subpackage is a bad experience, because

1. We'll still have to carry the current name anyway, as a transitional dummy;
2. Presumably the Qt5 package should just be phased out at some point; and
3. Package renames should really only be considered when the upstream project actually changes its name, not to correct our own (longstanding) violations of convention.