Skip to content

Switch to LGPL v2.1 #10

@selurvedu

Description

@selurvedu

If there is any reason for you to pick LGPL v2.0 specifically instead of v2.1, like creating libdecsync as a derivative of another work licensed under v2.0? If not, please consider upgrading the license.

LGPL v2.1 is essentially the same as LGPL v2.0, but it introduces clearer wording, making the same statements in a more unambiguous manner, and explaining the intentions and applicability of the license better than the old version. You can check the difference between version 2.0 and version 2.1 yourself, e.g. by using Meld, Kompare or an online tool like Diffchecker1.

In my humble opinion, there is only one new paragraph in v2.1 under Section 6 that makes a difference:

b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

*.so, *.dll and *.dylib are all shared libraries and you already provide your licensees with a permission to link their software (or, as the license calls it, "work that uses the Library") to libdecsync, so this paragraph should be acceptable for you.

Footnotes

  1. I tried to share a link to a saved comparison on Diffchecker, but the Save and Share buttons don't work for some reason.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions