[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: license issue: calling a GPLv2 library

From: David Kastrup
Subject: Re: license issue: calling a GPLv2 library
Date: Tue, 20 Jun 2006 12:43:46 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Alexander Terekhov <> writes:

> This is not an issue at all. Except in the GNU Republic. In reality,
> linking as such (especially dynamic one) is totally irrelevant 
> regarding (software) copyright. Ignore that utterly moronic GPL FAQ.
> Your options are:
> 1. Don't distribute the GPL'd stuff and let the users acquire it 
> separately:
>   users have all the rights to use and even adapt (create private
>   derivatives) of lawfully acquired stuff without "accepting" the 
>   GPL per 17 USC 117;

The problem is that if you are selling the user a package that is not
operative without linking to GPL code, the user is actually working as
your agent completing _your_ part of the deal when creating the
combined work.

The user _has_ the right to combine and use (as opposed to distribute)
code from you with GPLed code if he so desires.  But if the product is
not operative before linking to the GPLed code, it is pretty clear
that the total product, the stuff for which money has been exchanged,
includes the GPLed software.  Whether the final assembly is done by
the seller, or by the user on behalf of the seller as a part of
receiving a usable product, is irrelevant.

> 2. include it in your distribution package:
>   apart from "additional copies" distributed per 17 USC 117 it 
>   even falls under GPL's own "mere aggregation" clause.

Linking a library is not "mere aggregation".
Cf. <URL:>

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]