Pinentry for Qt4 still needed?
Dirk-Willem van Gulik
dirkx at webweaving.org
Wed Jul 14 22:44:10 CEST 2021
> On 14 Jul 2021, at 22:41, Damien Goutte-Gattat via Gnupg-devel <gnupg-devel at gnupg.org> wrote:
>> On Wed, Jul 14, 2021 at 10:55:34AM +0200, Ingo Klöcker wrote:
>> I'm currently working on (usability) improvements for pinentry-qt and I'm wondering whether pinentry-qt still needs to build with Qt4 or whether we can drop support for Qt4
> For what it’s worth , my take on this is that by now support for Qt4 should be on a "best-effort" basis. That is, as long as continuing to support Qt4 is not too much of a hassle, we might as well do it, but if it becomes a burden (and, in particular, if it starts to get in the way of usability improvements), I wouldn't have too many qualms about dropping it.
> (The only GNU/Linux distribution I know of that still does not provide Qt5 is the last release of Slackware (14.2, released in 2016), and even though I am a proud Slacker, I wouldn’t be too concerned about it. Many Slackers use -current (where Qt5 is available), and for those that still use 14.2, they have other problems – such as the fact that they are basically stuck with GnuPG 2.0…)
Macosx also relies on it until 2 revs ago - though that is not far of of going qt5 now as apple eols sometime later this year.
More information about the Gnupg-devel