Re: macho 0.4 released

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

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

 Anthony> At least, this is my understanding.

You are of course correct. I'm sorry for misstating the libiconv license
as GPL.

That still leaves some patent issues (which I've been already mentioning
on c.l.l a while ago), but in general the situation is a lot better.

That makes me wonder if anyone has done UFFI wrapping of libiconv.

--J.

_______________________________________________
Clump mailing list
[email protected]
http://manly.caddr.com/mailman/listinfo/clump

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/uIrSLth4/7/QhDoRAg9KAKDh6+jCh/UC5pOuN3strJ5XpvtrCwCgz6B8
T5W5fE7CIy9wvoFw+Cel/Tg=
=k7JK
-----END PGP SIGNATURE-----