-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> Hi both,
>
> in any case, we will need to make a decision about pinentry-tqt. As I understand, the code is now part of the
> upstream pinentry. Here are some ways to deal with this:
>
> 1. Add a separate git repository that will follow upstream pinentry but only pinentry-tqt will be built during
> build in TDE. There would have to be an occasional merge with upstream, but we should have our own branches, our
> own tags, out own issues tracking... just as we do with libtdevnc and libvnc upstream.
>
> 2. Add the pinentry-tqt code to tdeutils, as you mentioned. But this would mean manual synchronization between
> pinentry upstream and tdeutils.
>
> 3. Add only a mirror of pinentry git repository but not as part of the TDE umbrella. And the packages will be built
> completely outside the other TDE packages.
>
> What is your opinion?
>
> Cheers
>

Hi Slavek,
based on this and emails from Emanoil, I think we should go for option 1 and we include a pinentry-tqt-trinity as part
of tde.
Cheers
  Michele
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl5pnaIACgkQKnW3yore
1c/kaBAApbNZpWV0bMP6ol07C1rantRpqjvFWk+2Y62zOjbYgpkA4dlT3YX0A/x6
XMHI6EMRm3frmujQxZBorTiwA3+84DMga3ccKAev/0nLOfmOMPb1Qzwv31lhejkq
7lmtPRALWWgKp8qbXWcwxfALvjQOIybGT+rZjFiZSyOq8+6mIHcQ4mH2CRLwLo/g
SC5NnPfjMseyij6D4nQDyUd5OCQ7enXOOxG18m+SIxZtbhT58f1Ie6aXm1RygB9j
Ekp7VkZduo0HEN7f9i1XpiXPWTPEobAnjAuFLSxIV7AQK7t22SBLSvDXIKodW/+n
j1PmQ5XwqlxQ8gbkK8CWH0+jIQpwlMn/6OTEVsANuTsuz0jOQ/44WknhKfXumZip
ohJPmqdADCW1y/M55Xs5IBqGZ481EWcfIZrJBka39cm+oApGg3kdGzKWI/T3cLBI
dGEbst2YLdIIZhmY7uFIBU949LCbg4MI8zVcUVHFx8QjkCBcknPd6T1Gj8PrchK2
Mun52+gcxnHH6eu/X9pWW04PAyHQ/XbSjqm46jFpacOklcvchgnhLFBnI+AW16C9
a3kd8m+i6M2gky36dGC/Z2mLGgsK/HaxzVyUAwvmCsgSbCRjXNRi0B2eyUEkUFN4
qrEe2xnM1Gj1PIGMkiq8szIYBjaGgEhExy9NiFU3yJHs4qQkFxY=
=BuV6
-----END PGP SIGNATURE-----