In particular at the GPL FAQ I suggest the item for when the interpreter is GPLed. In there they address directly what should be a separate question, namely the case of libraries in an interpreted language. And their answer is that if you wish to use LWP, your program must be GPLed.

Note, however, that the advice given by the FSF is given by people interested in the most restrictive interpretation possible. OTOH that is advice determined by legal counsel, and were the GPL to go to court then that legal counsel's interpretation of their own license would have substantial weight in determining the interpretation of the license. IANAL, and I am not giving legal advice, but I personally would think twice before thinking that the FSF's interpretation would not therefore hold up in court.

I also note that the GPL has never been tested in court. This is both good and bad. It is bad because there are no rulings to clarify the possible legal readings. It is good because it means that every time the FSF has challenged a corporation on the GPL, the corporation had their legal eagles read the license, and the lawyers told the company to blink.

(For more on the enforcement techniques the FSF uses to get compliance, you can read Eben Moglen's description.)

In reply to Re (tilly) 2: licensing confusion by tilly
in thread licensing confusion by david54321

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.