On Thursday 13 February 2003 00:32, Matt Munz wrote: > All, > > Perhaps I'm dense for looking for a technological solution to an > ideological problem, but can't this be resolved with an abstraction layer?
Java is tricky since (L)GPL didn't consider the nature of Java when it was written/updated, read separate mail. > For example, Apache doesn't seem to mind the dependency on javax.xml.*. > Nevertheless, this allows one to use GNU-licensed libraries with Apache > products (http://www.gnu.org/software/classpathx/jaxp/). > > Couldn't a simple solution be that each time one wants to add a GNU feature > to an Apache project, they simply whip up a little abstraction layer, > license that layer under the APL, or whatever javax.xml.* is licensed > under, and then call it a day? > > The GPL is not a virus. It is a license, and, just like any other license, > it comes with restrictions. I don't see why those restrictions comprise a > justification for separating different groups of public software developers > from each other, resulting in the duplication of effort, expending time and > (scarce) resources. Unfortunately it is a virus. 1. A virus lives on/in a "host", in this case a software project. 2. It spread from one host to another over a medium or carrier, in this case by software dependency. I agree it is absolutely rediculous to split the OSS in two major camps and replicating efforts, but "my camp", IMSO, is the "free side", as I can utilize these efforts basically in any way I want, for instance, add value and release a commercial product based on the OSS infrastructure. GNU requires me that the "add value" is also GPL, which I don't call freedom. Maintaining source code to the "public" is not hazzle-free (another aspect of freedom), so even if I don't have any "commercial" or "secrecy" reasons to not-to-publicize the source code, GPL forces me to do so, in fact even if I could prove that noone in the world would be interested (which is not possible). > BTW, there are many other examples of abstraction layers that provide a > separation between code written under different licenses that nevertheless > need to interoperate, not the least of which is the OS interface itself. I assume that you are talking about things like; Linux APIs used by the JVM, but the JVM is not GPL... The GPL makes a minute differentiation between "static linking" (inside your code) and "dynamic linking" (.dll and .so), where the later doesn't require my dependency to be GPLed. Abstraction layers needs to be outside the non-GPL project, and the ASF project exposes one API/SPI, and the abstraction layer bridge the two. It is technologically not very difficult, but ASF will not be part of it. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
