You're mistaken, Wolfie. There are provisions in the Mozilla Public License to accommodate both open source and commercial/proprietary projects.
You're still, of course, bound by the MPL (with regard to providing source code for MPL-covered code), but if all you do is statically link against MPL-covered code, then all you need to do is make sure you comply with the terms for the stuff that was MPL-covered before you started.
http://www.mozilla.org/MPL/2.0/FAQ.html
Quote:
Q11: How 'viral' is the MPL? If I use MPL-licensed code in my proprietary application, will I have to give all the source code away?
No. The license requires that Modifications (as defined in Section 1.10 of the license) must be licensed under the MPL and made available to anyone to whom you distribute the Source Code. However, new files containing no MPL-licensed code are not Modifications, and therefore do not need to be distributed under the terms of the MPL, even if you create a Larger Work (as defined in Section 1.7) by using, compiling, or distributing the non-MPL files together with MPL-licensed files. This allows, for example, programs using MPL-licensed code to be statically linked to and distributed as part of a larger proprietary piece of software, which would not generally be possible under the terms of stronger copyleft licenses.
|
I believe we've had this discussion before.
