On Wed, 2006-04-19 at 07:21 -0500, Chris Adams wrote: > Once upon a time, Tom 'spot' Callaway <tcallawa@xxxxxxxxxx> said: > > Ehhh... right now there is no way (at least, none that I can think of) > > to update to newer versions of modules included in the base perl > > package, other than to get them updated in the base perl package. > > site_perl and vendor_perl are searched before the base perl install > directory, so installing modules there should override modules included > with perl (you don't need to replace files). > > However, I don't know how rpm would handle two different RPMs providing > the same 'perl(SomeModule)'. This latter point is the key one. It could potentially throw other perl packages for a loop when they rely on the modules provided by perl, but instead, find the newer modules. I think the best thing to try first would be to open a bugzilla ticket against perl asking for those specific module components to be updated (or perhaps moved to extras as their own components). ~spot -- Tom "spot" Callaway: Red Hat Senior Sales Engineer || GPG ID: 93054260 Fedora Extras Steering Committee Member (RPM Standards and Practices) Aurora Linux Project Leader: http://auroralinux.org Lemurs, llamas, and sparcs, oh my!
