With perl right now, licensing issues just aren't. You don't have to worry about the licenses on the modules your code uses if you don't actually ship them with your program, so most people don't even think about the ramifications of the licenses of the modules they use.
Once you start doing all-in-one packages, especially if you're shipping what's essentially a single binary, those license terms become far more important. A not insignificant number of perl modules are pure GPL, which can be an issue both if you don't want to release the source for your program and if you use other modules that use GPL-incompatible licenses. This isn't a problem with the current setup, as the restrictions are on distribution and not use, but once you start distributing...
Not a new issue in general, just one that perl's not had to deal with for the most part up until now.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.