Acme-Thing

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.

3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:

  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
     modifications in the Standard Version of the Package.

  b) use the modified Package only within your corporation or organization.

  c) rename any non-standard executables so the names do not conflict with
     standard executables, which must also be provided, and provide a separate
     manual page for each non-standard executable that clearly documents how it
     differs from the Standard Version.

META.json  view on Meta::CPAN

                        "name" : "FUNCTIONS",
                        "version" : "4.017"
                     },
                     {
                        "class" : "Pod::Weaver::Section::Leftovers",
                        "name" : "@Author::PERLANCAR/Leftovers",
                        "version" : "4.017"
                     },
                     {
                        "class" : "Pod::Weaver::Section::Region",
                        "name" : "@Author::PERLANCAR/postlude",
                        "version" : "4.017"
                     },
                     {
                        "class" : "Pod::Weaver::Section::Completion::GetoptLongComplete",
                        "name" : "@Author::PERLANCAR/Completion::GetoptLongComplete",
                        "version" : "0.08"
                     },
                     {
                        "class" : "Pod::Weaver::Section::Completion::GetoptLongSubcommand",
                        "name" : "@Author::PERLANCAR/Completion::GetoptLongSubcommand",

META.yml  view on Meta::CPAN

            -
              class: Pod::Weaver::Section::Collect
              name: FUNCTIONS
              version: '4.017'
            -
              class: Pod::Weaver::Section::Leftovers
              name: '@Author::PERLANCAR/Leftovers'
              version: '4.017'
            -
              class: Pod::Weaver::Section::Region
              name: '@Author::PERLANCAR/postlude'
              version: '4.017'
            -
              class: Pod::Weaver::Section::Completion::GetoptLongComplete
              name: '@Author::PERLANCAR/Completion::GetoptLongComplete'
              version: '0.08'
            -
              class: Pod::Weaver::Section::Completion::GetoptLongSubcommand
              name: '@Author::PERLANCAR/Completion::GetoptLongSubcommand'
              version: '0.04'
            -

README  view on Meta::CPAN

     }

  Why?
    Now comes the harder question: why use Perl module/distribution to
    represent seomthing at all, other than an actual Perl module? Releasing
    as Perl distribution and module leverages a few things: 1) the CPAN
    distribution metadata (see CPAN::Meta) where a distribution can depend
    (relate) to other modules (other things); 2) the CPAN infrastructure
    where revisions of the thing can be released, distributed, tested, and
    installed to target systems; 3) the OO feature of the Perl language
    where a user can interact with a thing (e.g. download a TV series poster
    or trailer, etc).

    Of course, none of the above suggest that a generic representation like
    "Acme::Thing" is better than a more specific one, e.g.
    "WebService::ISBNDB" for books.

HOMEPAGE
    Please visit the project's homepage at
    <https://metacpan.org/release/Acme-Thing>.

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

=head2 Why?

Now comes the harder question: why use Perl module/distribution to represent
seomthing at all, other than an actual Perl module? Releasing as Perl
distribution and module leverages a few things: 1) the CPAN distribution
metadata (see L<CPAN::Meta>) where a distribution can depend (relate) to other
modules (other things); 2) the CPAN infrastructure where revisions of the thing
can be released, distributed, tested, and installed to target systems; 3) the OO
feature of the Perl language where a user can interact with a thing (e.g.
download a TV series poster or trailer, etc).

Of course, none of the above suggest that a generic representation like
C<Acme::Thing> is better than a more specific one, e.g. C<WebService::ISBNDB>
for books.

=head1 HOMEPAGE

Please visit the project's homepage at L<https://metacpan.org/release/Acme-Thing>.

=head1 SOURCE