3 ms·

I think the LGPL is becoming particularly irrelevant. I’d like to use GEOS (LGPL 2.1) in a macOS app but the risks are high as you point out. I think it’s going

I think the LGPL is becoming particularly irrelevant. I’d like to use GEOS (LGPL 2.1) in a macOS app but the risks are high as you point out. I think it’s going to be significantly less risky long run to rebuild GEOS in Swift. The complexity and lack of clarity in the licensing is a real burden. I don’t think this is the spirit of the LGPL - it’s just code signing prevents the use of dynamically linked libraries in the way LGPL intended.

Expurple 1y ago
Perhaps you'll find MPL 2.0 less complex and more "in the spirit of the LGPL": https://www.reddit.com/r/rust/comments/msjil9/opinions_on_the_mozilla_public_license_v20_for/ https://www.reddit.com/r/rust/comments/msjil9/opinions_on_th... https://www.reddit.com/r/opensource/comments/msjk93/licensing_question_mozilla_public_license_20/ https://www.reddit.com/r/opensource/comments/msjk93/licensin... https://www.reddit.com/r/opensource/comments/1g2sprd/could_anyone_explain_the_difference_between_lgpl/ https://www.reddit.com/r/opensource/comments/1g2sprd/could_a... Although that won't help you with GEOS, which is already licensed as LGPL-only.