view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

Source code for a work means the preferred form of the work for making
modifications to it.  For an executable file, complete source code means
all the source code for all modules it contains; but, as a special
exception, it need not include source code for modules which are standard
libraries that accompany the operating system on which the executable
file runs, or for standard header files or definitions files that
accompany that operating system.

  4. You may not copy, modify, sublicense, distribute or transfer the
Program except as expressly provided under this General Public License.
Any attempt otherwise to copy, modify, sublicense, distribute or transfer
the Program is void, and will automatically terminate your rights to use
the Program under this License.  However, parties who have received
copies, or rights to use copies, from you under this General Public
License will not have their licenses terminated so long as such parties
remain in full compliance.

  5. By copying, distributing or modifying the Program (or any work based
on the Program) you indicate your acceptance of this license to do so,
and all its terms and conditions.

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

=head1 NAME

Acme::CuckooMith - lays an egg in another bird's nest

=head1 DESCRIPTION

This modules is a basic test to see if it is possible to have the toolchain
recognize a module under one name, while the actual distribution installs it
under a completely different name, as well as seamlessly loads it under a
different package name in Perl.

If successful this will be a proof-of-concept of forking a module into a
different public name, while still providing the end user most of the advantages
of having the code in the original namespace.

Preliminary result: Even under the Acme namespace there are plenty smokers who
will result alse fails because of this. The correct solution in the future will
be to install the modules into a harmless sub-path of lib which can then either
be added to @INC via a module, or copied over into the proper location via user