Alt

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.19 Mon Dec 29 14:24:59 PST 2014
 - Add PERL_ALT_INSTALL to docs

0.18 Mon Dec 29 08:03:15 PST 2014
 - Update docs regarding versioning

0.17 Sun Dec 28 19:50:06 PST 2014
 - Update docs with new best practices

0.16 Sat Aug 16 14:52:27 PDT 2014
 - Fix Meta copyright

0.15 Sat Aug 16 14:41:50 PDT 2014
 - Change Meta email

0.14 Sat Aug 16 10:42:42 PDT 2014
 - Meta 0.0.2

LICENSE  view on Meta::CPAN

TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) 19yy  <name of author>

README  view on Meta::CPAN

    Obviously, this completely overlays the old Foo::Bar install, but that's
    the whole idea. The user isn't surprised by this because they just asked
    for an Alternate implementation. If they don't like it, they can simply
    reinstall the original Foo-Bar, or try some other alternate.

ALT BEST PRACTICES
    This idea is new, and the details should be sorted out through proper
    discussions. Pull requests welcome.

    Here are the basic guidelines for best using the Alt namespace:

    Name Creation
        Names for alternate modules should be minted like this:

            "Alt-$Original_Dist_Name-$phrase"

        For instance, if MSTROUT wants to make an alternate IO-All
        distribution to have it be Moo-based, he might call it:

            Alt-IO-All-Moo

lib/Alt.pod  view on Meta::CPAN

Obviously, this completely overlays the old Foo::Bar install, but that's the
whole idea. The user isn't surprised by this because they just asked for an
B<Alt>ernate implementation. If they don't like it, they can simply reinstall
the original Foo-Bar, or try some other alternate.

=head1 ALT BEST PRACTICES

This idea is new, and the details should be sorted out through proper
discussions. Pull requests welcome.

Here are the basic guidelines for best using the Alt namespace:

=over

=item Name Creation

Names for alternate modules should be minted like this:

    "Alt-$Original_Dist_Name-$phrase"

For instance, if MSTROUT wants to make an alternate IO-All distribution to