Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#5608 closed enhancement (fixed)

openldap-2.4.40

Reported by: Fernando de Oliveira Owned by: blfs-book@…
Priority: normal Milestone: 7.7
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

Change History (7)

comment:1 by Armin K, 10 years ago

FYI,

conftest.c:150:2: error: #error "BerkeleyDB 6.0.20+ license is incompatible with LDAP"
 #error "BerkeleyDB 6.0.20+ license is incompatible with LDAP"

configure: error: BerkeleyDB version incompatible with BDB/HDB backends

comment:2 by Fernando de Oliveira, 10 years ago

Owner: changed from blfs-book@… to Fernando de Oliveira
Status: newassigned

comment:3 by Fernando de Oliveira, 10 years ago

Fixed at r14475.

Leaving open for proper rephrasing of license problem.

comment:4 by Fernando de Oliveira, 10 years ago

Owner: changed from Fernando de Oliveira to blfs-book@…
Status: assignednew

comment:5 by bdubbs@…, 10 years ago

I think the license issue is not valid. From http://www.oracle.com/technetwork/database/berkeleydb/downloads/licensing-098979.html is says:

"Oracle employs a dual licensing model that offers customers a choice of either our open source license or a commercial license. Our open source license is OSI-certified and permits use of Berkeley DB in open source projects or in applications that are not distributed to third parties. Our commercial license permits closed-source distribution of an application to third parties and provides business assurance."

If it's ok for open source projects, then it's ok for openldap.

I will remove the warning and then close this ticket after commit unless I hear a different opinion first.

comment:6 by bdubbs@…, 10 years ago

Resolution: fixed
Status: newclosed

Fixed now at rev 14477.

Thinking about it, if there is a problem with the bdb package, the warning should have been there, not with openldap.

comment:7 by Armin K, 10 years ago

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
https://fedoraproject.org/wiki/Changes/BerkeleyDB_6#Summary
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.

Note: See TracTickets for help on using tickets.