From: Arjan van de Ven <arjan@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
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 15:37:49 +0200 [thread overview]
Message-ID: <1114004269.6238.72.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1114002429.774.45.camel@localhost.localdomain>
On Wed, 2005-04-20 at 09:07 -0400, Steven Rostedt wrote:
> On Wed, 2005-04-20 at 14:57 +0200, Arjan van de Ven wrote:
> > On Wed, 2005-04-20 at 08:49 -0400, Steven Rostedt wrote:
> > > 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.
> >
> > it does, as long as you provide the .o files of your own stuff so that
> > the end user can relink with say a bugfixed version of library.
>
> I don't see that in the license. As point 5 showed: "Such a
> work, in isolation, is not a derivative work of the Library, and
you missed the point "in isolation". If you do NOT link against the lib,
eg your app in isolation, you don't have to care abuot the LGPL. That is
what it says. The moment you do link you are no longer "in isolation".
next prev parent reply other threads:[~2005-04-20 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 17:57 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
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 [this message]
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=1114004269.6238.72.camel@laptopd505.fenrus.org \
--to=arjan@infradead.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 \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®