Message: previous - next
Month: April 2013

Re: [trinity-devel] TDE Status Report

From: "Timothy Pearson" <kb9vqf@...>
Date: Sun, 7 Apr 2013 16:34:21 -0500
> On Friday 05 April 2013 6:59:48 pm you wrote:
>> Hi all,
>> After discussions with the core development team, I have realised
>> that I owe everybody a long overdue update regarding Trinity.
>> I apologise for the relatively long term silence on these mailing
>> lists. Like most people, I have to work in order to keep the lights
>> on and the servers humming, and these commitments have taken time
>> away from TDE.  In particular over the past several months I have not
>> had any spare time to dedicate to TDE, which is why most development
>> (other than Slavek's tireless patching) had appeared to grind to a
>> halt.
> I am somewhat confused on how Trinity dev works. I have been using the
> 14.0 nightlies with Debian Wheezy for quite a few months now. There
> always seems to quite a few packages updated. Just yesterday the
> following:
> '29 packages upgraded, 0 newly installed, 0 to remove and 0 not
> upgraded.'
> From my experience with Debian, the release of new packages stops, and a
> good period of time to test the release.  I am a little nervous about
> the number of new packages. What triggers new packages?

Packages are updated whenever I manually run the "nightly" autobuild
script; this is *typically* done when I think the GIT tree is in a usable
state and that the resultant packages should work.  This should be
automated to run every night (hence the name), but the TDE archive grew
too large for that to be feasible some time ago.  I am working on
upgrading the build system to provide a true nightly build, but this is
slow work due to TDE's almost nonexistent financial support. ;-)