view release on metacpan or  search on metacpan

lib/App/lcpan/Manual/Internals.pod  view on Meta::CPAN

passes are more high-level and/or experimental and/or optional.

=head3 Third step pass 1: content, scripts, distribution metadata, dependency

First we list the content of each release archive and store the results into the
C<content> table. This will allow us to check whether a distribution has a
distribution metadata file (F<META.yml> or F<META.json>), whether a distribution
contains scripts, and so on.

We populate the C<script> table by heuristically including content which from
its name looks like script, e.g.:

 script/foo
 bin/whatever

We then extract the distribution metadata files (either F<META.json> or
F<META.yaml>) and store the information contained in these metadata files into
the database. These include the distribution name (written to the C<dist> table)
and the dependency information (written to the C<dep> table).

At the end of this first pass, we have a pretty useful database already. One of