[kde-community] Licensing question with header-only libraries

[Jaroslaw Staniek]

On 24 January 2016 at 09:37, Ivan Čukić <ivan.cukic at kde.org> wrote:

> Hi all,
>
> I'm preparing a library that will probably end up being a header-only
> library.
> I would like to use a license like LGPL - the code in question needs
> to stay free, but that it can be used from non-free code like it is
> the case with other frameworks.
>
> The issue is that (if I'm correct) LGPL does not have anything
> different to GPL in this case since this is not a library that is
> dynamically linked - if someone uses it, its code becomes a part of
> the end product.
>
> If the above is correct, I think we should add a GPL+exception to the
> list of approved licences.
>

Hi Ivan
​I'd go with LGPL+exception​​. It's effectively the same as GPL+exception
in this context but shows the intent of providing a library. If someone
ever transforms the code to a regular library + headers, no change will be
needed: LGPL will work for linkable code, and LGPL+exception for the
embeddable headers.

​Cheers.
​


>
>
> --
> KDE, ivan.cukic at kde.org, http://cukic.co/
> gpg key id: 850B6F76
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community




-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20160124/457b7de5/attachment.htm>