3 ms·
Why is it licensed under Apache and MIT? The underlying GTK is LGPL, so this is just creating extra licenses in a users project for no good reason.
by phkahler 4y ago
Why is it licensed under Apache and MIT? The underlying GTK is LGPL, so this is just creating extra licenses in a users project for no good reason.
- sigzero 4y agoApache or MIT "if" you make the choice. But yeah, that is kind of strange to do it that way.
- mixedCase 4y agoBecause the author preferred to share their code under that license is the only reason you actually need. Additionally, there's an added benefit if you're building non-(L)GPL software with it: you can just use the compiler defaults (statically link Relm4, dynamically link Gtk) and stay compliant.
- bluejekyll 4y agoFor those unfamiliar with Rust, the Rust language and a lot of the foundational ecosystem are dual-licensed with MIT and Apache. For any Rust project, this is not a surprising default for the licensing choice. Here’s a good discussion on it: https://internals.rust-lang.org/t/rationale-of-apache-dual-licensing/8952/2 https://internals.rust-lang.org/t/rationale-of-apache-dual-l...
- phkahler 4y agoThis makes the most sense of all the answers. Either matching the GTK license, or the common Rust app licenses is reasonable. I think I would have gone the other way, but that's just me.