On Sat, 2008-08-30 at 00:02 +0200, Dag Wieers wrote: > On Wed, 27 Aug 2008, Karanbir Singh wrote: > > >> should explore the problem further with TUV and the CentOS > >> community. If a fix is not forthcoming from TUV, I reluctantly suggest > >> that we get together with the CentOS people and fork this portion of > >> the distro, perhaps standardizing on Perl 5.10 . There are people > >> in the Perl community ready to assist us. > > > > While forking the whole perl subsection of the distro is a bit > > drastic, I am quite happy to have a perl in C5Plus. Does someone want > > to get in touch with Keith and get a summary on what needs fixing in > > this case ? Also - if the conversation was to take place on > > centos-devel list, would be much cooler. > > > > Upstream have said the fix will be in 5U3, and considering that might > > be still a few months away, could we get something sorted before then > > ? > > To be honest, if this problem was part of RHEL5 since its inception and > only a few people until now have actually been bugged by it. I don't see a > good reason to release something now only because someone was able to make > a big poo out of it and got to slashdot. > > We do not want to give attention-seekers more airtime, before we know it > everyone who finds a bug starts shouting. > > (Don't read me wrong, of course it should be fixed, I am just concerned > about the motives and the generality of this bug wrt. other bugs.) +1 My 2cents: Build a package using the patches from the f8 package. Test it for the change in speed. Put it up somewhere people can get to it easily and post a note in the centos bug report on it and on the rh bugzilla report where the centos build is that fixes the problem. that's it. the people who care can fix their problem until there's a final upstream fix and you don't give any more airtime to the people yelling about it. -sv