[Bug 474044] Review Request: libzdb - A small, fast, and easy to use database API

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=474044





--- Comment #11 from Tom "spot" Callaway <tcallawa at redhat.com>  2009-02-12 10:18:12 EDT ---
Well, the EXCEPTIONS does not violate the GPLv3. It grants additional rights,
not restrictions. It is clearly derived from the MySQL linking exception, but,
it is not identical.

The MySQL exception says:

"A FOSS application developer ("you" or "your") may distribute a Derivative
Work provided that you and the Derivative Work meet all of the following
conditions:"

The libzdb EXCEPTIONS says:

"You are free to distribute the Program and link the Program with Work licensed
under one or more of the Open Source licenses listed below in section 2, as
long as:"

The wording here is precise, the GPLv3 defines the term "the Program" as:

"“The Program” refers to any copyrightable work licensed under this License.
Each licensee is addressed as “you”."

This is different from a derived, or modified work, which is given a separate
definition in the GPLv3:

"To “modify” a work means to copy from or adapt all or part of the work in a
fashion requiring copyright permission, other than the making of an exact copy.
The resulting work is called a “modified version” of the earlier work or a work
“based on” the earlier work."

So, since EXCEPTIONS explicitly grants linking exceptions to "The Program", but
not to "modified versions", it only applies to an unmodified libzdb.

Since we are making modifications (and even if we were not, because we would
want the right to do so), we cannot leverage the EXCEPTIONS. However, we are
not required to do so (which is why it doesn't violate the GPLv3), so we choose
not to.

The historical reference is made to show that the upstream's intent in with
EXCEPTIONS shows a reasonably malicious history. Accordingly, where we might
assume ignorance in the choice of wording in the EXCEPTIONS text in a similar
scenario, we can not in this specific case.

I would advise that we not package the EXCEPTIONS file, as it is of little
value to anyone.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.