Bug 437817

Summary: RFE: Upgrade Module::CoreList to 2.14
Product: [Fedora] Fedora Reporter: Ralf Corsepius <rc040203>
Component: perlAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: kasal, rc040203, robin.norwood, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-18 12:37:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 437804    

Description Ralf Corsepius 2008-03-17 15:39:06 UTC
Description of problem:
Module::CoreList-2.13 seems defective.
cf. https://bugzilla.redhat.com/show_bug.cgi?id=437804

Upstream recommends to upgrade to 2.14.

Module::CoreList is one of the "dual-lived" perl modules, which would mean we
have to alternatives to choose from:
a) Reactivate the (currently) retired perl-Module-CoreList package
b) To replace the Module::CoreList in Fedora's "perl" package.

What would you prefer?

I am in favor of a), because it would provide a more flexible solution, which
would avoid having to rebuild "perl" (Allowing this option had been one purpose
of the perl-package split). Downside: core-perl would be build against an
outdated Module::CoreList (2.13). Also, I am not sure if yum can handle this.

But I also don't have much of a problem with b) - It would be less flexible and
a bit more effort.

Comment 1 Marcela Mašláňová 2008-03-18 12:37:35 UTC
I prefer B. It will be in rawhide soon.

Comment 2 Ralf Corsepius 2008-03-18 13:48:47 UTC
(In reply to comment #1)
> I prefer B. It will be in rawhide soon.
<sigh/>
I regret having to say so, but your decision is a "slipped-by" opportunity ;)

a) would have been a precedence for a perl-dist package being provided by
different src.rpms (old from perl, new from separate package).
It would have been an opportunity to demonstrate a better, closer and more
flexible coupling of perl to CPAN: "If a core package is too old/broken",
replace it with an external one ("dual-lived" in Perl terms).

Anyway, you chose your poison ;)