It is unlikely that Artistic licensed modules will get you into trouble. But it can. And has.
I don't remember whether they were still Hip Communications or ActiveState, but they were shipping a binary version of Perl for Windows, named Perl, without contributing back code changes. That was a no-no. Read the license if you don't believe me. This was many moons ago and was resolved peacefully with Perl 5.005 incorporating ActiveState's changes. (This happened partly through the wisdom of Larry Wall et al, partly through the intervention of Tim O'Reilly, and partly through ActiveState's willingness to risk ticking off Microsoft.)
However you are right that it is virtually impossible to conflict with the Artistic License by accident. But corporate legal may find that verifying this is harder than they want - particularly if they are afraid that code which is claimed to be under the Artistic might turn out not to be...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.
|
