On Mon, Dec 10, 2012 at 1:04 PM, Francesco Poli
<invernom...@paranoici.org> wrote:
> Even if there's no *direct* linking of libgdm3 with libssl, it is my
> understanding that there is indeed an issue, as long as one single
> binary executable is linked with both libgdm3 and libssl.
>
> I believe that this follows from Section 3 of the GNU GPL v2.
> gdbm is the "Program" released under the terms of the GNU GPL v2 or
> later.
> The binary executable linked with it is "a work based on it" (according
> to the FSF's legal theory of linking, which is usually assumed to be
> valid by the Debian Project, in order to stay on the safe side...),
> and Section 3 states, in part:
>
> |   3. You may copy and distribute the Program (or a work based on it,
> | under Section 2) in object code or executable form under the terms of
> | Sections 1 and 2 above provided that you also do one of the following:
> |
> |     a) Accompany it with the complete corresponding machine-readable
> |     source code, which must be distributed under the terms of Sections
> |     1 and 2 above on a medium customarily used for software interchange; or,
> |
> [or other methods to make the source available...]
>
> Hence, one has to make the source code available under the terms of
> Sections 1 and 2, that is to say, among other things "licensed as a
> whole at no charge to all third parties under the terms of [the GNU GPL
> v2]" (see clause 2b).

I follow your reasoning and it makes sense to me.

However, Section 2 defines a "work based on it [the Program]" as a
modification. We are not making any modification to it.
Nevertheless, I see how you can argue that, according to the FSF and
Section 2b, ntop "contains" libgdm3.

So basically, are you telling me that *any* code that is dynamically
linked against a gpl library is automatically relicensed under GPL,
including the python interpreter for example? This does not sound
right to me...

Cheers,
Ludovico


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to