in reply to LWP vs ExtUtils::Installed vs libwww::perl vs Module::Metadata

I took a quick look at the source, this code is what is responsible for incorrectly turning auto/libwww/perl/.packlist into libwww/perl.pm. Personally I'd consider this a bug, or at least a "limitation" that occurrs when the location of the .packlist file(s) don't match the module names (but rather the distribution names). This appears to be true of the four modules named in this node, and if one were to analyze the other ~38k CPAN distros, I'm sure there's more out there.

Replies are listed 'Best First'.
Re^2: LWP vs ExtUtils::Installed vs libwww::perl vs Module::Metadata
by Anonymous Monk on Sep 24, 2018 at 20:05 UTC
    I was hoping someone with more perl wisdom would know where to look and what to look for. Thank you haukex! ExtUtils::Installed->modules() outputs module names (and apparently the occasional dist, oops) and Module::Metadata reads module names or files (but not dists). These core modules are very reliable and designed to work together. Anyway when ExtUtils::Installed->modules() sends a dist name to Module::Metadata->new_from_module() and the lookup fails, the solution is to send that dist name back to ExtUtils::Installed->files() to get a list of the module files, which Module::Metadata->new_from_file() understands. Thank you for helping me realize what's happening and fix a very old and annoying bug (in my code).
[reply]

In Section Seekers of Perl Wisdom