trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] Adding new API/ABI features to TDE

From: Darrell Anderson <humanreadable@...>
Date: Fri, 30 Mar 2012 09:48:28 -0700 (PDT)
> That is because you guys are the only ones building trinity
> nightly on a daily basis :-)
> 
> I am steadily working through different bug reports at a
> crawling pace, and expect many of them to be pushed by R14. I have
> not even looked at any build problems as bug reports. I consider
> build bugs problems for packagers ( you ) and I let you resolve them
> because at this point you have a very good idea of how it works. I see
> there are a few marked as PATCHAVAIL. why not push those patches now
> that you have write access?
> 
> Don't forget they have been using kde3.5 for quite some time
> I suspect, and are currently using Trinity 3.5.12. While R14
> may have bugs we _are_ getting through many of them.
> 
> I concur with the sentiment, only to then say "Yes, such is
> the plight of finite time and energy"

Yes, I understand very much the concept and reality of limited resources. :)

I am encouraged by your words. I realize that some members might be working quietly without noticeable "noise." I look forward to your patches. I know about some of them and am happy that they will improve Trinity in meaningful ways.

The thing about packagers is we are not automake and cmake experts. We learn but we post to the list because we are stumped. Yesterday I was given a simple one-liner fix for libksquirrel and the package built. These things are not obvious to all packagers and that is why we ask for help. Perhaps one day I'll see those solutions as being obvious but that day is not today. I'm good at exposing these problems but not always at fixing. :)

Regarding those build related bug reports that have patches. Yes I have commit access but I know from experience that a patch is not always good for all people. The patch always works great for the person submitting the patch but has no way to test the effects on other systems. I saw this a lot back with 3.5.12 when I first joined the project. I probably pushed Tim to swearing at times because everything worked on his Debian/Ubuntu systems and I would break them on my Slackware systems. For that reason I am not eager to push patches until others using different systems test the patches.

Darrell