On Sat, 07 Dec 2024 15:02:24 +0100 Werner Koch via Gnupg-devel <gnupg-devel@gnupg.org> wrote:
>Hi! > >On Sat, 7 Dec 2024 11:56, Andreas Metzler said: > >> gpa is due to be removed from Debian/testing since it uses gtk2. gpa git >> has gtk3 conversion, so we could switch to GIT head. However I am not > >Actually I still use GPA for testing things, in particular new GPGME >features. That is because I find it much easier to hack on GPA than on >Kleopatra/Libkleo. Compiles faster and the code is easier to >understand. > >I have not done releases because my co-developers convinced me that it >is better to concentrate on one GUI frontend and they want Kleopatra. >Frankly we are putting a huge amount of work and money into Kleopatra >and it won't be easily to get GPA to the same level of UX. > >That said, I don't known whether it makes sense to keep GPA in Debian. >Building from source is easy enough and that is sufficient for having >GPA as a testbench. > >If there are enough voices to keep GPA as binary package, I would spend >some time on making a new release. But in the long run we need an >upstream maintainer for GPA. I can't promise to do that; there are >anyway too many things I have to care about. > I have helped with gpa previously, and done the GTK3 conversion, but after this message I definitely feel that it's time to abandon it. (And my contributions going to waste, a shame, but not much one can do about that). If Kleopatra is where the resources (and money) go, then what's the point in wasting (unpaid) time on GPA? This message makes it very clear where the focus is. /Andreas Rönnquist gus...@librem.one andr...@ronnquist.net _______________________________________________ Gnupg-devel mailing list Gnupg-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-devel
