I don't see what the problem is. It's known that Debian is very picky on license issues. It's also known that Perl *isn't*, that Larry *doesn't* want a very tight license (there's a reason that the AL is vague - the AL is a declaration of intend, and not a legal document like the GPL), and that most CPAN authors don't really care (hence the "under the same terms as Perl" clause).

Frankly, I don't think Perl or the CPAN authors should change. If Debian wants a strong position on licensing, good for them. If that means they have to drop software from their distribution, than that's the price they pay. It's their choice. I'm all for free software, but I loathe all the hassle that surrounds licensing.

I'm a Debian user myself and I couldn't care less whether some Perl module from CPAN was included or not. If you can't type

perl -MCPAN -eshell cpan> install Foo::Bar Quux::Fnurd

you're probably not going to use those modules anyway. There's lots of software I like to use. Do you really think I won't use it because it wasn't included on the Debian CDs I own? Come on.

Programmers won't collectively flee to Python just because Debian doesn't include a bunch of freely available CPAN modules on their CD's.

Abigail


In reply to Re: Licensing of Perl Modules by Abigail-II
in thread Licensing of Perl Modules by dondelelcaro

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.