indexing does not match PAUSE behaviour when meta 'provides' is present

[karenetheridge]

This issue: rjbs/Dist-Zilla#510 led me to discover that the presence of incomplete provides metadata in the *19 release was causing PAUSE to not extract any $VERSIONs for any of the modules in this distribution. This is correct, as when provides is present, it is deemed to be authoritative and the .pm files are not scanned. However, metacpan's indexing algorithm is behaving differently. Is META.* not being used as part of the indexing process?

11:52 < ether> in what repository does the indexing code live? it's not metacpan-web, is it?
11:53  * ether found that META.* doesn't seem to be taken into consideration in the same way that PAUSE uses it, so indexing results can differ.
11:59 < ranguard> ether: cpan-api repo
11:59 < ether> danke!
12:02 < ranguard> ether: https://github.com/CPAN-API/cpan-api/blob/master/lib/MetaCPAN/Script/Release.pm I _think_
12:04 < ranguard> Good place to start if nothing else

[karenetheridge]

This code mirror's PAUSE's algorithm:

    my $pmparser = Parse::PMFile->new($metadata);
    my $packages_info = $pmparser->parse($pmfile);
    #print Dumper($packages_info);
    print sprintf('%30s', 'Parse::PMFile module(s): '), join(', ', keys %$packages_info), "\n";
    print sprintf('%30s', 'Parse::PMFile version: '), ($packages_info->{$module}{version} // '<undef>'), "\n\n";

[tsibley]

Related to #336.