Poor choice of words on my part. I did mean distribute/include CPAN modules in the code you sell -- that's why I mentioned packaging -- you can architect the app in such a way that any reliant CPAN modules are *outside* your app.

However, I think you and moritz, while pointing out good issues, failed to grasp the most important point of my original post (but maybe that's because I didn't do a good job of writing it). My point is this:

If you're going to sell a perl application, and said application depends on CPAN modules, you *must* investigate the license(s) of those modules and if there are restrictions, either architect around the restrictions or negotiate a different license with the author(s) ... just saying, "oh it's on CPAN, it's under the same license as perl" can get you into a lot of trouble.

-derby

In reply to Re^3: Selling your Perl app by derby
in thread Selling your Perl app by whakka

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.