Re: macho 0.4 released

I just thought I'd put my 2 cents in.  LGPL'ed software can be included 
in any software, regardless of its license (even proprietary software).  
The LGPL states that changes to the library itself (libiconv, here) as 
well as derivative works (if you were to fork libiconv) must be released 
under the LGPL.  But any software which uses the library is unbound by 
its license.

That was the entire point of having a Library (now Lesser) GPL.  To 
allow the library itself remain free while fostering broader adoption by 
removing the viral nature of the GPL w.r.t. the software using the library.

At least, this is my understanding.

Anthony W. Juckel

Edi Weitz wrote:

>On Tue, 11 Nov 2003 00:46:07 -0800, Jan Rychter <[email protected]> wrote:
>
>  
>
>>There is always GNU libiconv
>>(http://www.gnu.org/software/libiconv/), but it's GPL. I am not sure
>>if I understand the legal implications of accessing it via an FFI.
>>    
>>
>
>It's the LGPL. IIRC, the Unicode support of Scieneer Common Lisp is
>based on libiconv, so unless Scieneer has broken the license it is
>either OK to include it in proprietary software or they have a special
>agreement with the libiconv authors.
>
>Edi.
>_______________________________________________
>Clump mailing list
>[email protected]
>http://manly.caddr.com/mailman/listinfo/clump
>  
>