-=| Niko Tyni, Fri, Dec 19, 2008 at 09:08:41AM +0200 |=-
> On Fri, Dec 19, 2008 at 07:33:13AM +0200, Damyan Ivanov wrote:
> > I assume that the whole purpose of CoreList is to say whether a given 
> > module is to be found in the core Perl distribution or is it to be 
> > found on CPAN or somewhere else. For this kind of classification, 
> > Miniperl is a "core" module and should be reported.
> 
> Is this just aesthetics, or are you actually using ExtUtils::Miniperl
> for something?

Not really.

I discovered that it is not reported by Module::CoreList when I tested 
a routine in dh-make-perl that is supposed to find Debian packages, 
corresponding to a given Perl module. It needs a way to determine if 
a given module is a core one and assume it is contained in 
perl-modules. So the test just blindly invokes the routine on all 
modules found in /usr/{share,lib}/perl/$Config{version}/ and complains 
if some of them is not reported as a core module. All pass, except for 
ExtUtils::Miniperl.

The problem I have at hand is that M::CoreList does not match what is 
actually shipped.

> I see it was removed from the CPAN side in 2002
> (ExtUtils-MakeMaker-5.50_01) with the rationale that it's not useful to
> anyone outside the Perl core.

I think usability is not relevant here. Is ExtUtils::Miniperl a core 
module or not? How is that judged?

My (admittedly naive) criteria is "does it come with perl" and 
therefore I think Module::CoreList is wrong here. I also fail to see 
why EU::Miniperl is still considered "core" in perls up to 5.9.5, but 
not after that.

If EU::Miniperl is not useful for anything else, but only for building 
perl, then it should not be shipped at all. That's where my initial 
doubt has come from -- is this a bug in M::CoreList or maybe 
EU::Miniperl should not be shipped.

It is my belief that this still stands -- either EU::Miniperl is not 
to be shipped with perl from 5.10.0 on and M::CoreList is correct, or 
EU::Miniperl is to be shipped, is therefore "core", and M::CoreList 
has a bug.

Sadly there is no reply to the RT bug :/

-- 
dam            JabberID: [email protected]

Attachment: signature.asc
Description: Digital signature

Reply via email to