Closed pombredanne closed 3 years ago
It is not really feasible for us to change the license. If you want to ship software that uses TPIE and not release that software under GPL or LGPL v3, you should build tpie as a shared library.
@antialize Thank you for the quick reply! Can you elaborate a bit on the "not feasible" part?
We do not require that contributes to TPIE hand over the copyright of their contributions to some TPIE organization, so to change the license would require us to get permission from each an every committer. We did that when we changed from GPLV2 to LGPLv3, but that was a very complicated process that I and none of the other maintainers want to do again.
This project is OLD, the first commit is from 1994, but the code is older still. Some of the authors have not touched the project in decades, and are quite busy with other things.
@antialize This makes sense. Thank you++
From what I can see the default is to build the library for static linking per https://github.com/thomasmoelhave/tpie/blob/7c11771f6320c50ab59f795e85a1d7c6e69b06e1/CMakeLists.txt#L72
Typically, this may be a problem with the LGPL, as the caller may be subject to the LGPL too. The way this is handled is usually with an exception. For instance this exception from Canonical: https://raw.githubusercontent.com/go-xmlpath/xmlpath/v2/LICENSE
Would you consider granting such exception here too?