-=| Dominic Hargreaves, 19.01.2012 20:34:57 +0000 |=-
> On Tue, Jan 17, 2012 at 07:04:23PM +0100, Marc Lehmann wrote:
> > Neither perl, perl-base nor perl-moduels contain the .packlist file that is part
> > of a standard perl installation.
> >
> > This file is needed when programs want to know which files belong to the
> > perl core, and which don't.
>
> Can you give an example of a program which uses it like this?
>
> > To reproduce, use:
> >
> > perl -e 'do ".packlist"'
> >
> > on a working perl, this should cause lots of compiletime errors (Bareword
> > missing...) because the .packlist file is not valid perl.
>
> This isn't a great test case.
Trying to guess what the real use case is, here's a one-liner that
seems to not work as one would expect:
perl -MExtUtils::Installed -we' print
ExtUtils::Installed->version("Module::CoreList");'
Apart of taking several minutes of disk juggling to finish, it concludes
that "Module::CoreList is not installed", which is an outright lie :)
Of course, there is another way to get the module version (require
Module::CoreList; print $Module::CoreList::VERSION), which for some
reason is not usable to ExtUtils::Installed.
Maybe this gives a clue to somebody.
Attachment:
signature.asc
Description: Digital signature