Re: Re: pinentry-tqt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dne st 11. března 2020 Michele Calgaro via trinity-devel napsal(a):
> On 2020/03/11 03:48 PM, deloptes wrote:
> > Michele Calgaro via trinity-devel wrote:
> >> Hi Emanoil, see here
> >> https://bugs.pearsoncomputing.net/show_bug.cgi?id=2830 Feel free to
> >> prepare PR for that :-)
> >>
> >> Cheers Michele
> >
> > Thank you, I now remember - it belongs to tdeutils.
> >
> > I have some questions Michele - why 14.2 ? I was hoping 14.1 is the
> > candidate. - and as it is upstream in gnupg, how should I proceed. I
> > recall there was something in git to track the original source.
> >
> > I do not think I fully qualify for creating PR for this particular
> > case. Can you advise?
> >
> > thanks
>
> When we selected the list of thing to finalize R14.1.0 we tried to go by
> priority, functionality and required dev time. We had a long list of
> things and bug and we had to make choices. So pinentry-tqt went into
> R14.2.0 list ultimately .
> If you can summarize what work is require for this bug and you want to
> work on it, we may be able to squeeze it in for R14.1.0.
> Keep in mind we want to release R14.1.0 before the end of the year.
> Cheers
>   Michele
>

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
-- 
Slávek

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Trinity Users]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [KDE]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux