From: Steven Rostedt <rostedt@goodmis.org>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: linux-kernel@vger.kernel.org, Karel Kulhavy <clock@twibright.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
linux-os@analogic.com, Chris Friesen <cfriesen@nortel.com>
Subject: Re: GPL violation by CorAccess?
Date: Wed, 20 Apr 2005 08:49:58 -0400 [thread overview]
Message-ID: <1114001398.774.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1113982209.3803.7.camel@gimli.at.home>
On Wed, 2005-04-20 at 09:30 +0200, Bernd Petrovitsch wrote:
>
> As long as they do not statically link against LGPL (or GPL) code and as
> long as they do not link dynamically agaist GPL code. And there are
> probably more rules .....
>
Actually, I believe that the LGPL allows for static linking as well. As
long as you only interact with the library through the defined API, it
is OK.
>From the LGPL preamble:
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
Point number 5 of TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION:
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
So, I would say that the LGPL _does_ allow statically linked to non GPL
work.
-- Steve
next prev parent reply other threads:[~2005-04-20 12:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 17:57 GPL violation by CorAccess? Karel Kulhavy
2005-04-19 18:25 ` Lennart Sorensen
2005-04-19 18:32 ` Charles Cazabon
2005-04-19 18:59 ` Chris Friesen
2005-04-19 19:19 ` Richard B. Johnson
2005-04-19 19:59 ` Chris Friesen
2005-04-19 21:44 ` Richard B. Johnson
2005-04-19 23:37 ` Chris Friesen
2005-04-20 0:26 ` Richard B. Johnson
2005-04-20 7:30 ` Bernd Petrovitsch
2005-04-20 12:49 ` Steven Rostedt [this message]
2005-04-20 12:57 ` Arjan van de Ven
2005-04-20 13:07 ` Steven Rostedt
2005-04-20 13:36 ` Michael Poole
2005-04-20 13:37 ` Arjan van de Ven
2005-04-20 17:18 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114001398.774.40.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=bernd@firmix.at \
--cc=cfriesen@nortel.com \
--cc=clock@twibright.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=lsorense@csclub.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.