Hi all,
- Original Message -
Yes, there also seems to be some confusion with GPL and LGPL.
Even if Eigen was not additionally lisenced as GPL2+, the main license
is LGPL3 and not GPL3 so a GPL2 prog (or even a proprietary program)
can use it without problem.
Ah yes, I didn't
Alex Fraser alerted me to fact blender has some GPL3 code (which
implies blender IS GPLv3 AFAIK).
This is a bit of a problem because 'elbeem' is version 2 only.
GPL2 ONLY, no 'version 2 or later' clause
1 ./intern/elbeem/extern/elbeem.h:4: * All code distributed as part of
El'Beem is
Hi,
Eugen:
http://eigen.tuxfamily.org/index.php?title=Main_Page#License
http://eigen.tuxfamily.org/index.php?title=Main_Page#Licenseis OK for GPL2
Regards
Sergey
___
Bf-committers mailing list
Bf-committers@blender.org
Hi,
For as long as possible, I'd prefer to stick to 2 or later.
For all code committed to Blender that has been the default anyway,
also when not explicitly mentioned.
- the gpl3 py scripts then need update
- elbeem wouldn't be an issue I'm sure (will ask Nils Daniel Genscher)
- eigen
Yes, there also seems to be some confusion with GPL and LGPL.
Even if Eigen was not additionally lisenced as GPL2+, the main license is
LGPL3 and not GPL3 so a GPL2 prog (or even a proprietary program) can use it
without problem.
2011/2/6 Sergey Kurdakov sergey.fo...@gmail.com
Hi,
Eugen:
