I agree it is a problem to get applications working that require a lot of non-core-distribution modules. But I do not think packing everything into the Perl distribution is a good idea. I am also not sure anymore if installing application-specific modules into the standard site_perl directories is always good, either. If you have many applications running on the same system, you sometimes want incompatible versions of the same CPAN module, for example.

I think large Perl applications should include all their dependencies in their own library path, and small applications should get their modules from a user_perl path. In both cases, you do not need superuser rights to manage these installations, which is especially good for shared hosting. Both is already possible, even with the CPAN tool, but it could maybe get easier. For example, when a non-root user does CPAN install it could install into a user_perl directory that would also be automatically recognized by the Perl runtime.

Let me put here my short list.

That list would be very different for everyone. If you include Class:DBI, CGI::Application, Kwiki (very application specific stuff) it will make it difficult to argue where to draw the line.

In reply to Re: Larger Perl distributions by Thilosophy
in thread Larger Perl distributions by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.