help-octave
[Top][All Lists]
Advanced

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

Re: "LGPL API" (was: Re: Private company and code salvation)


From: Sergei Steshenko
Subject: Re: "LGPL API" (was: Re: Private company and code salvation)
Date: Mon, 29 Sep 2008 10:55:09 -0700 (PDT)



--- On Mon, 9/29/08, John W. Eaton <address@hidden> wrote:

> From: John W. Eaton <address@hidden>
> Subject: "LGPL API" (was: Re: Private company and code salvation)
> To: "David Bateman" <address@hidden>
> Cc: address@hidden
> Date: Monday, September 29, 2008, 7:14 AM
> On 29-Sep-2008, David Bateman wrote:
> 
> | Acceptance is subject to the degree to which community
> members believe 
> | the GPL should be the license to all software. However,
> the harder 
> | question is "how can you have an LGPL, or other
> license, to a set of 
> | libraries using the GPL?"
> 
> I don't think you can.  Once you link some code
> licensed under the
> LGPL with some other code licensed under the GPL, you must
> distribute
> the result under the terms of the GPL.  So it is not
> possible to avoid
> the terms of the GPL by simply inserting an interface
> covered by the
> LGPL between non-free code and code covered by the GPL.
> 
> jwe

Linux kernel is GPL, ALSA is LGPL, I believe ALSA site claims one can
created closed-source audio applications based on ALSA.

ALSA drivers are loaded dynamically if Linux kernel is compiled so,
ALSA lib - the thing end user needs for his/her audio application - is
a DLL - IIRC.

Regards,
  Sergei.


      


reply via email to

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