> Putting LGPL code in the main program is a no go because that would require relicensing the whole > thing to LGPL.
I don't think so. Since MIT is compatible with GPL. Since LGPL is even less copyleft, then it should be a lesser problem.
Re-licensing the whole thing is not needed. Most authors don't accept such code because they want the whole application to be of same license.
Take for an example - Tomboy. It contains code with MIT, GPL and LGPL in one same codebase.
> Putting LGPL code in the main program is a no go because that would require relicensing the whole
> thing to LGPL.
I don't think so. Since MIT is compatible with GPL. Since LGPL is even
less copyleft, then it should be a lesser problem.
Re-licensing the whole thing is not needed. Most authors don't accept
such code because they want the whole application to be of same
license.
Take for an example - Tomboy. It contains code with MIT, GPL and LGPL
in one same codebase.