-----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:
- 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.
- Add the pinentry-tqt code to tdeutils, as you mentioned. But this would mean manual synchronization between
pinentry upstream and tdeutils.
- 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
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting