At 08:34 AM 4/4/02 -0500, Charles Marcus wrote: >like it could be the answer. The only question is, can OOo use it? > >OOo requires that anything integrated into its source code be made >available to them under the terms of the LGPL license.
The LGPL license is much more restrictive than the Apache license which has almost no restrictions at all. AFAIK, there is no problem in integrating FOP into an LGPL product. But if you want FOP to be licensed under LGPL you have a problem, because I think that the Apache license doesn't allow changing the license of it's software. My question is why does OOo require FOP to be LGPLed? You can integrate it into OpenOffice without it being LGPL. If you do this it would also be fair if you contribute changes to FOP back to the Apache tree. Just as another side note: I consider the LGPL and GPL a bad license. LGPL projects can profit from code under more liberal licenses like BSD, MIT, X11, Apache, but the other way round is not possible. There are other drawbacks also... Best regards, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
