| |||||||||||||
Relicensing and rebasing LibreOfficeRelicensing and rebasing LibreOfficePosted May 28, 2012 20:43 UTC (Mon) by akumria (subscriber, #7773)In reply to: Relicensing and rebasing LibreOffice by simosx Parent article: Relicensing and rebasing LibreOffice
Then, presumably, a company wanting to make a commercial product based upon LibreOffice will want to assist in making the portions they need into a robust library they (and others) can re-use.
Then that component can just call into the library, no?
(Log in to post comments)
Relicensing and rebasing LibreOffice Posted May 29, 2012 5:41 UTC (Tue) by jamesh (guest, #1159) [Link]
Well, that might not help if the target platform doesn't allow the user to replace the library in their copy of your application (e.g. iOS).
Also, if the code you're interested in is common to both LibreOffice and Apache OpenOffice, then why bother creating a library when you could just use the Apache code under the ASL?
|
|||||||||||||