Jeremy Whiting wrote: > On Sun, Aug 30, 2015 at 8:48 AM, Jeremy Whiting <[email protected]> wrote: > > Hey all, > > > > I may have found another candidate for unmaintained. KGpg is a ui for > > gnupg. I've never used it, but have used kleopatra. Anyway, here's my > > reasoning. Please fix any false assumptions I may have made if you > > know kgpg or kleopatra better than I: > > > > 1. KGpg does gnupg. Kleopatra also does, but is maintained. > > 2. KGpg has not been ported to Qt5/kf5, Kleopatra has. > > 3. KGpg isn't part of kdepim nor is it maintained by the PIM team, > > Kleopatra is. > > > > Is there anything that KGpg does that Kleopatra doesn't/can't do? Or > > is there any reason to port KGpg to Qt5/kf5 and keep releasing it?
> Correction, KGpg is maintained, Rolf made commits as late as last > month. My mistake. I gave KGpg a try here and it does seem to work > well. Rolf, could you use a hand porting it to Qt5/KF5 ? I did not port for the reason that KGpg depends on kdepimlibs (KABC), which had no Qt5-based release yet (now it has), and I must confess I can occupy my time with other stuff and was too lazy to build it from git. In fact I was asked at least twice why there was no KF5-port and both were also too lazy to build kdepimlibs stuff themself. Now that there is a release it makes actually sense to port, so I hope I can manage it in time for 15.12. If someone is bored and wants to assist I will not reject any efforts. Kleopatra can do X.509, which KGpg can't. I never found that really missing. And KGpg looks so much more beautiful ;) And it has the CAFF mode, which I doubt Kleopatra has. And it supports photo ids, which I was told was intentionally left out of Kleopatra for some policy reasons. Eike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
