#5608: openldap-2.4.40
-------------------------+--------------------------
Reporter: fo | Owner: blfs-book@…
Type: enhancement | Status: closed
Priority: normal | Milestone: 7.7
Component: BOOK | Version: SVN
Severity: normal | Resolution: fixed
Keywords: |
-------------------------+--------------------------
Comment (by Krejzi):
The problem is not in license itself, but in an incompatibility between
different OSS licenses. Current AGPLv3 license is incompatible with
anything that isn't GPLv3+ as far as I am aware of, and OpenLDAP license
looks like kind of BSD license to me.
I believe you can't link to a GPLv3 code (AGPLv3 being GPLv3 like license)
unless your code is GPLv3 too, given that GPLv3 is incompatible with
GPLv2. That's why FSF came up with LGPL, a license mainly used by
libraries that give an opportunity to link LGPL code even into proprietary
products, while enjoying other benefits of GPL(-like) licenses.
https://en.wikipedia.org/wiki/License_compatibility [[br]]
https://fedoraproject.org/wiki/Changes/BerkeleyDB_6#Summary [[br]]
http://www.infoworld.com/article/2611450/open-source-software/oracle-
switches-berkeley-db-license.html
Again, I'm not into software licensing, and this is all new to me, but
I've made some assumptions in this reply from information that I gathered
around web.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/5608#comment:7>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
