SCIENTIFIC-LINUX-USERS Archives

August 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Reply To:
Konstantin Olchanski <[log in to unmask]>
Date:
Tue, 26 Aug 2008 11:24:35 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
On Tue, Aug 26, 2008 at 08:58:40AM -0700, Keith Lofstrom wrote:
> http://blog.vipul.net/2008/08/24/redhat-perl-what-a-tragedy/

Please read the explanation written by the person who fixed
the relevant perl performance bugs:

http://use.perl.org/~nicholas/journal/37274

From reading his cvs commit comments, it looks like the issue is
performance bugs fixed back in October 2007, but never propagated
to the version packaged by Red Hat.

I am surprised at the ranting & raving, as this situation has happened
before and we know exactly how to deal with it:

1) 1st tier distributor (Red Hat) pushes a bum package (today it's perl,
yesterday it was bum kernels)

2) 2nd tier distributor (SL or CENTOS) fixes it (bum kernels) or does
not fix it due to manpower and experitise limitations (bum perl).

3) 3rd tier distributor (TRIUMF computing group) fixes it for
the local site (or does not fix it)

4) end user fixes it locally on his machine (build from source,
installs fixed RH rpms linked from the bugzilla bug entry,
or installs Fedora rpms, whatever).

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2