add LGPLv3 linking exception for header-only GR4 #403
Conversation
This commit adds the LGPLv3 linking exception to handle GR4 as a header-only library. The exception allows proprietary applications to link and use GR4 without disclosing their source code, addressing legal and operational constraints (e.g., in government or security-sensitive applications). This is particularly important since traditional dynamic or static linking isn't applicable in header-only libraries. Modifications to GR4 itself remain LGPL-compliant, ensuring continued adherence to copyleft and FLOSS principles while enabling wider adoption. By including this exception, we aim to increase the flexibility for adoption by public organisations, critical infrastructure, and industry partners, while maintaining the core FLOSS principles. Signed-off-by: Ralph J. Steinhagen <r.steinhagen@gsi.de>
There was a problem hiding this comment.
Thanks for the PR.
While reviewing the PR and examining the licensing details, I also summarized the discussion of the proposed changes. I'm not entirely sure if I captured everything accurately, but this is mainly for my own understanding.
This exception clarifies that the library can be used in both static and dynamic linking without requiring the application’s source code to be disclosed.
The main changes are:
-
Easier integration with proprietary code: Users can link the library to proprietary applications without releasing the application’s source code, while still having to contribute back changes to the library itself.
-
Clarifies header-only use: The linking exception helps address ambiguities in LGPL-3.0 related to "linking" and "combined work" in header-only libraries, which are commonly used.
-
Maintains copyleft spirit: The core idea of contributing improvements to the library is preserved, while allowing broader industry adoption.
The PR can be merged.
This commit adds the LGPLv3 linking exception to handle GR4 as a header-only library. The exception allows proprietary applications to link and use GR4 without disclosing their source code, addressing legal and operational constraints (e.g., in government or security-sensitive applications).
This is particularly important since traditional dynamic or static linking isn't applicable in header-only libraries. Modifications to GR4 itself remain LGPL-compliant, ensuring continued adherence to copyleft and FLOSS principles while enabling wider adoption.
By including this exception, we aim to increase the flexibility for adoption by public organisations, critical infrastructure, and industry partners, while maintaining the core FLOSS principles.