Provide separate libraries for LGPL components
Ember uses a number of Ogre related components that are licensed under the LGPL. Amongst these are Caelum and the PLSM. These are provided with the Ember source since a) they are not very stable yet b) I've made some changes to them to get them to work better with Ember. They are however statically linked into the main Ember compilation, and therefore relicensed as GPL, as required by the GPL and allowed through section 4 of the LGPL.
I would however very much rather respect the original LGPL license as chosen by the authors of these components. In order for that to work they must compiled, installed and loaded as third party plugins. This isn't so hard to do since they originally are designed for such purposes, but it requires some changes to how they now work within the Ember system. There's no need to provide them in a separate source package, as long as they are detachable from the main Ember code (i.e. in a sole subdirectory). But they must be compiled as .so or .dll files and loaded dynamically at runtime.
Blueprint information
- Status:
- Complete
- Approver:
- Erik Ogenvik
- Priority:
- High
- Drafter:
- Erik Ogenvik
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Erik Ogenvik
Related branches
Related bugs
Sprints
Whiteboard
After reading up on how GPL and LGPL can be combined a little more I've come to the conclusion that it's very much possible to statically link LGPL code into a GPL work, and retain the original LGPL license. The final work will however be licensed under GPL only. Thus this blueprint becomes obsolete.
We should also revert those headers that were transformed from LGPL into GPL.