> Just replying out loud.....
> 
> I can see that some of the comment from datamation maybe is
> waranted.
> 
> For me the fustration is building a package from git repo
> say tdebase on a 
> monday then working on several other packages and then
> update the local git 
> repo rebuilding tdebase on friday results in tdebase not
> building at all.  
> Possibility due to a commit/patch/update in the
> source.  I have since 
> abandoned building from git and only use the 3.5.13
> tarballs which have 
> worked well for me.
> 
> My question is before a commit is made does whoever 
> changed/updated/patched/crunched/mutilated the code, first
> see if it builds 
> without barfing/puking then do the commit?
> 
> As for running TDE in general (which I have run it
> exclusive since I finished 
> the arch linux build scripts last month) I have not
> experienced any breakage 
> etc except for a few things in some of the apps that are
> minor and I can wait 
> them until someone gets to fixing them so I don't see any
> big problema with 
> running TDE.

GIT is not the same as an official release. I expect GIT to break occasionally. That's okay.

Backporting patches to an official release is not the same as backporting all changes in GIT since the official release. Those types of patches would be extracted from GIT and made available as separate patches.

I would guess before any official point release anouncement that at least three packagers from different distros would test the backporting, both from a build and usability perspective.

Darrell