> Not to mention utterly unenforceable. Consider:
>
> 1) Oracle Corp. builds their database for Linux on a Linux system.
> 2) Said system comes with standard header files, which happen in this case to
> be GPL'd header files.
> 3) Oracle Corp.'s database becomes GPL.
>
> There's not a court in the civilised world that would uphold the GPL in that
> scenario.
I do believe, however, that in these cases the header files in question are
under the LGPL, which does specifically allow linking and #including in non-GPL
and non-LGPL code.
In my opinion, this whole thing would just go away (including some of
Microsoft's anti-GPL rants), if the FSF officially declared that under the GPL,
#including a GPL header file does NOT force your code to be also GPL.
-- Timur Tabi - ttabi@interactivesi.com Interactive Silicon - http://www.interactivesi.com- 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/