lkml.org 
[lkml]   [2005]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: GPL violation by CorAccess?
From
Date
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".


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-04-20 15:42    [W:0.050 / U:17.776 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site