Since the last week, we have been posting new additions to sipXportLib which heavily uses templates. These are header only implementations that requires no linking since it is inlined and parsed during compile time. right now these headers are published under the LGPL. AFAIK, LGPL allows a none open source end product to be linked to it and still without affecting its actual commercial license for as long as linking is done through a shared library. This gives the liberty for end users of the product to upgrade or recompile the said LGPL library independently of the closed source application. Templates, being header-only, implementations cannot be shared since they need to be compiled with the application and any change to these template headers requires that the application using them must also be recompiled. This defeats LGPL making the templates only usable in open source applications that are compatible with LGPL. Having said this, does it make sense to have an alternative LGPL compatible license to these headers like http://www.boost.org/users/license.html or do we maintain LGPL and make sure that our libs only allows an application to link to it if it is licensed under an open source compatible license?
Joegen _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
