[PATCH pinentry 4/4] tqt: Disable echoing if backspace is pressed first.

Damien Goutte-Gattat dgouttegattat at incenp.org
Wed Mar 11 22:08:17 CET 2020

On Wed, Mar 11, 2020 at 09:03:29PM +0100, deloptes wrote:
>pinentry-tqt is working perfectly well on the TDE desktop

Since I don’t use TDE myself and therefore can’t fully test pinentry-tqt 
in its “natural” environment, I am glad to read that.

>Was it merged in gnupg? Can and should it be merged?

Yes, I merged it into the main branch back in November 2017, it is part 
of the last pinentry release (1.1.0, published in December 2017).

>As the TDE release 14.1 is planned to happen by the end of this year, I
>was wondering if we have to do something to finalize the work already

At the source level, I don’t think so, especially since you say that 
pinentry-tqt is working well.

I guess the hurdle that TDE users will need to overcome though is 
getting pinentry-tqt installed on their system. A quick search through 
the repositories of some common GNU/Linux distributions (Debian, Ubuntu, 
Fedora, Arch) tells me that none of them are packaging pinentry-tqt, and 
this is unlikely to change since they don’t package TQt either.

I see that the TDE project provides its own packages for the most common 
distributions, so it would make sense for you to provide a binary 
package for pinentry-tqt as well. Make a binary package that provides 
*only* pinentry-tqt (disable all other pinentries at the configure 
step), and provide it along with the other TDE packages.

>How we can setup our repository to follow the main branch?

Not sure I understand your question here.

If you have changes to pinentry-tqt (e.g. fixes for bugs reported by TDE 
users), the “standard” workflow would be to clone the pinentry main 
branch from git.gnupg.org, do your development on a dedicated branch, 
them send the patches to gnupg-devel. From there I (or another GnuPG 
developer) would take care of merging them.


- Damien
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20200311/dace673c/attachment.sig>

More information about the Gnupg-devel mailing list