Thanks for all the great feedback all!

Because I opt to put all of my CPAN modules under the standard Perl license (and always have), I'm going to try to keep it that way.

If a library is released under the GPL (not the LGPL), does that mean that any software which uses it has to be under the GPL or a GPL-compatible license?

Yes, because the software as it is actually run includes the library.

Because my code is not compiled before it is actually installed, my distribution will not contain any code of the included library. It's only during the make process that the libs are sucked in. This leads me to believe that this is a copyright issue (like anonymonk said in Re: When linking to a C library, do I need to use its license?), as I am directly using API calls into the library, but only after a user links the two.

I think what I'll do here is contact the author, state what I'm doing, and see if I can get a blanket exemption (license and copyright) in writing, so long as I never include any code.

If that fails, I'll give my lawyer a couple hours worth of work, and if it can't be sorted within that time, I'll just GPL the code and remove the Artistic license.

In reply to Re: When linking to a C library, do I need to use its license? by stevieb
in thread When linking to a C library, do I need to use its license? by stevieb

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.