I'm writing a new distribution, RPi::OLED::SSD1306 (code only on Github currently, will eventually make it onto the CPAN) that allows control of certain OLED displays directly via Perl.

This new distribution directly includes BSD-licensed C code and header files (Adafruit's ssd1306_i2c) which get built for the XS side of things, therefore, I believe I must BSD-license my entire new Perl distribution.

Now, I've got a top-level Raspberry Pi Perl distribution (RPi::WiringPi), that requires and returns objects of various other RPi:: distributions (sensors, ICs, protocols etc, you can see them all on my CPAN page).

I have written all of the existing RPi:: distributions myself, and they are all licensed as the same terms of perl itself.

My question is, if I have to re-license the top-level RPi::WiringPi distribution if I require the new RPi::OLED::SSD1306 distro, and it gets built along side of it automatically.

I'd like to keep it with the Perl license on my RPi::WiringPi dist, so worst case I figure, is that I write in the documentation for the OLED, but make a note (and throw a warning) that the OLED dist needs to be installed separately, due to it being of a different license. This way, the user has the option to install it or not.

In reply to Licensing clarification: Requiring a BSD licensed dist in a Perl licensed dist 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.