pinentry-tqt for the trinity desktop (former KDE3/Qt3 code)

[deloptes]

Thank you for the instructions and taking your time to answer.

I wonder if Damien could help with the autotools stuff. It would ease the
enormously process.

regards

On Wed, Oct 11, 2017 at 4:43 PM, William L. Thomson Jr. <wlt-ml at o-sinc.com>
wrote:

> On Wed, 11 Oct 2017 08:57:54 +0200
> deloptes <deloptes at gmail.com> wrote:
> >
> > What are the next steps?
>
> I did the recent pinentry-efl. https://dev.gnupg.org/T2905
>
> The steps are as follows give or take
>
> 1. Open task on dev.gnupg.org and attach a patch of your
> contribution. This will need to include modifications to
> autotools/build system, complete patch. Which includes a NEWS entry.
> Example - https://dev.gnupg.org/D426
>
> 2. You need to send a copy of the DCO to this list for your
> contributions to be accepted.
> https://dev.gnupg.org/source/gnupg/browse/master/doc/DCO
>
> Then just follow up on the task addressing any issues till its
> accepted. Fairly simply process but may take a bit of time.
>
> > I uploaded (hacked) version of pinentry-0.9.7 here
> > https://bugs.trinitydesktop.org/show_bug.cgi?id=2830
> > One could get the tqt subdirectory out of it. Unfortunately I did not
> > spent that much time fixing all the autotool stuff, but as I said I
> > hacked it so that it could build the pinentry-tqt binary.
>
> Ideally want to do the autotools stuff. That way a dev can apply patch
> and test directly. More you do, easier it is for others to test, and
> makes acceptance smoother and faster.
>
> --
> William L. Thomson Jr.
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/gnupg-devel/attachments/20171011/7a163653/attachment-0001.html>