Re: [trinity-devel] Re: pinentry-tqt

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