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 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
therefore falls outside the scope of this License." So you don't need to
do anything more than supply the source of the LPGL work. In fact, it
may not be a good idea to add a bugfixed version of the libary without
going through the vendor. You don't know if the application that uses
this depends on the side effects of the bug.

-- Steve


-
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:11    [W:0.038 / U:4.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site