On Fri, Jul 13, 2007 at 07:04:20AM +0200, Harald van Dijk wrote: > > >Correct, it does, just like it permits C applications with > > >GPL-incompatible licenses to link with GPL libraries, so long as this > > >linking is done by the end user and the application is not distributed > > >in its linked form. See for example the NVidia kernel module, or for a > > >somewhat different but similar example, cdrtools. > > > > Not true: > > > > cdrecord and "all-1" programs in cdrtrools are 100% CDDL. > > > > mkisofs is a GPL project that links to non-GPL libraries. > > This is something that is no problem with the GPLv2 as long as the > > libraries are not derived from or written for GPL code. > > > > As the libraries mkisofs links with are older than mkisofs or at > > least written independently and usage neutral, there is no problem > > even with binaray redistribution of mkisofs. > > http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs > > Neither the FSF nor you hold the copyright to mkisofs, but still, I'll > take the FSF's own interpretation over yours. If others believe you're > right, that's their choice.
Besides, as I recall, the decision for cdrkit was based on a disagreement over the build system license, not the license of libraries. Sorry, that's what I should've said, and that's all I should've said; the rest is not relevant here. -- [EMAIL PROTECTED] mailing list
