Message: previous - next
Month: May 2012

Re: [trinity-devel] Preparing updates for 3.5.13

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 1 May 2012 19:18:12 -0500
> On Tuesday 01 of May 2012 22:23:12 Timothy Pearson wrote:
>> Are you referring to a potential source tarball release?  If
>> so,
>> yes, it might be a good idea to release such a point update soon.
>> It would make everything easier for me to do that if a full patch file
>> could be provided that would apply cleanly to the extracted TDE sources
>> from the complete 3.5.13 tarball--this would avoid having to republish
>> the
>> 3.5.13 tarballs, which would add several gigabytes of files to the
>> already
>> strained mirror system.
>> Tim
> Yes, I mean what we refer to
> My goal was to prepare an update so that it could replace existing
> packages
> from 3.5.13 (not to occupy more space). So that users who install the
> Trinity
> according to the instructions given update automatically. I assumed then
> you
> can simply move the packages from my PPA to the official.

Yes, this is correct.  I am waiting to do so until I get an official
sign-off that the new packages work better than the old ones (i.e. users
are reporting that the new packages do not crash, etc.).
> In the source packages, patches have kept separately from the original
> sources
> (in debian/patches/bp*.diff). I was hoping they might be incorporated into
> Git branch for 3.5.13. I understand that you wanted a big diff instead of
> the
> set of patches?

Honestly I'm not sure how to do this in anything resembling a sane manner
in GIT.  I was considering distribution of the large patch file as an
update to the existing 3.5.13 sources, but comments and discussion are
definitely welcome on this subject!