My understanding of LGPL is that any code that 'statically' links to a LGPLd library should also be open sourced. In the C/C++ world LGPL kind of works o.k since the library is provided in a DLL form and hence the commercial projects can keep their value add closed.
1) Are there any links that provide clarification on how LGPL applies to script environments.
2) A page or two that explains what guidelines commercial projects that want to use bitweaver as the foundation shoud follow would be very helpful. Like which libraries can be used and not have to open up the source code.
3) This is especially important now that bitweaver is being positioned as a framework as opposed to just a system.
Comments
How does LGPL apply to a scripted environment?
kind of works o.k since the library is provided in a DLL form and hence the commercial projects can keep their value add closed.
1) Are there any links that provide clarification on how LGPL applies to script environments.
2) A page or two that explains what guidelines commercial projects that want to use bitweaver as the foundation shoud follow would be very helpful.
Like which libraries can be used and not have to open up the source code.
3) This is especially important now that bitweaver is being positioned as a framework as opposed to just a system.