I am curious why Rhino is under an MPL 1.1/GPL 2.0 dual license as opposed to the tri-license.
There's a large body of very useful Apache-licensed Java source out there, so non-trivial Java apps are likely to use some. Since the Apache licenses and GPLv2 are deemed incompatible by the FSF, the GPL option effectively vanishes leaving only MPL 1.1. And MPL is known to be a problem if one wants to get code in Debian... Are there any plans to add the LGPL option to Rhino? (If GPLv3 indeed ends up being Apache License 2.0-compatible, the GPLv2 "or later" language will take care of this with time assuming that Debian approves of GPLv3.) (I don't have an immediate need to get any particular code in Debian.) -- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/ _______________________________________________ legal mailing list [email protected] https://lists.mozilla.org/listinfo/legal
