Module::Metadata 's package_versions_from_directory() is confused by the existence of a fatscript.pm file in the directory being searched. The function pushes modules into the results that are inside the fatscript.pm: POD examples, etc. The fatscript.pm in question comes from from my cpanminus install and was made by App::FatPacker.
/home/myuser/perl5/lib/perl5/App/cpanminus/fatscript.pm
You can see this if you grab the file explicitly with new_from_file()
% cd ~/perl5
% perl -MData::Dumper -MModule::Metadata -E '
$pm_info = Module::Metadata->new_from_file("App/cpanminus/fatscript.pm" );
print Dumper \$pm_info ;'
It was suggested that the fatscript code was confusing Module::Metadata by the use of HERE style documents: the output shows "A" "My" "YourModule" etc. which all come from POD examples. Perhaps embedded fatpacked modules should ibe excluded by Module::Metadata somehow on a default run (via the call to wanted in the find() from package_versions_from_directory) and flagged as fatpacked with embedded modules and then either special cased (package_versions_from_fatpack) or the output only available when a constructor option is passed. In any case the incorrectly included POD example modules in the fatpacked file should be handled more correctly.
Module::Metadata 's
package_versions_from_directory()is confused by the existence of afatscript.pmfile in the directory being searched. The function pushes modules into the results that are inside thefatscript.pm: POD examples, etc. Thefatscript.pmin question comes from from mycpanminusinstall and was made byApp::FatPacker.You can see this if you grab the file explicitly with
new_from_file()It was suggested that the fatscript code was confusing
Module::Metadataby the use of HERE style documents: the output shows"A""My""YourModule"etc. which all come from POD examples. Perhaps embedded fatpacked modules should ibe excluded byModule::Metadatasomehow on a default run (via the call towantedin thefind()frompackage_versions_from_directory) and flagged as fatpacked with embedded modules and then either special cased (package_versions_from_fatpack) or the output only available when a constructor option is passed. In any case the incorrectly included POD example modules in the fatpacked file should be handled more correctly.