view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    eventually get to it :-), or perhaps when I get some help).

CREATING AN ACME::CPANLISTS MODULE

    The first step is to decide on a name of the module. It must be under
    the Acme::CPANLists:: namespace. Since, unlike in Acme::CPANAuthors, a
    module can contain multiple lists, you can just use your CPAN ID for
    the module, even if you want to create many lists, for example:
    Acme::CPANLists::PERLANCAR. But I recommend that you put each list into
    a separate module under your CPAN ID subpackage, for example:
    Acme::CPANLists::PERLANCAR::Unbless or
    Acme::CPANLists::PERLANCAR::Task::PickingRandomLinesFromFile.

    Inside the module, the two main package variables you have to declare
    are:

     our @Author_Lists = ( ... );
     our @Module_Lists = ( ... );

    Obviously enough, @Author_Lists contains author lists while
    @Module_Lists contains module lists.

lib/Acme/CPANLists.pm  view on Meta::CPAN

0.090

=head1 CREATING AN ACME::CPANLISTS MODULE

The first step is to decide on a name of the module. It must be under the
C<Acme::CPANLists::> namespace. Since, unlike in Acme::CPANAuthors, a module can
contain multiple lists, you can just use your CPAN ID for the module, even if
you want to create many lists, for example: L<Acme::CPANLists::PERLANCAR>. But I
recommend that you put each list into a separate module under your CPAN ID
subpackage, for example: L<Acme::CPANLists::PERLANCAR::Unbless> or
L<Acme::CPANLists::PERLANCAR::Task::PickingRandomLinesFromFile>.

Inside the module, the two main package variables you have to declare are:

 our @Author_Lists = ( ... );
 our @Module_Lists = ( ... );

Obviously enough, C<@Author_Lists> contains author lists while C<@Module_Lists>
contains module lists.