Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I interpreted the conflict clause differently (explicit clause vs no clause = a conflict), but I can understand this interpretation as well.

If I understand correctly, the derived work would be distributed under the Combined License (say, GPLv3). How can these additional obligations be enforced if they are not part of the license the combined work is distributed under?

In other words, I believe that when it says GPLv3 on the tin, I am meant to comply with the GPLv3, not some additional obligations enforced by a different license. But perhaps the situation is more nuanced than that?



yes, but it's really unclear

like I wouldn't even rely on the "no further restrictions" clause being valid/legally binding and due to how it works pretty much any previous case trying to enforce it I'm aware of failed (but on a technicality _not_ applying here). (As an example for a invalid clause, the automatic contract voiding on violation clause is not valid in some(all?) EU countries!)

and then the definition of derived work, especially in the EU and with GPLv2, is much less ... clear ... then what the FSF likes to claim.

so I think you really would need to ask a lawyer in any situations where it does matter


Does it say GPLv3 on the tin, or does it say "Compatible with GPLv3"?

If you mix BSD and MIT code, the result doesn't suddenly become one or the other, but rather a combination of both, right?


  > Does it say GPLv3 on the tin, or does it say "Compatible with GPLv3"?
As per [1], it says GPLv3 on the tin.

  > If you mix BSD and MIT code, the result doesn't suddenly become one or the other, but rather a combination of both, right?
The two pieces of code retain their original license, but you can distribute the combined work under just BSD.

[1] https://interoperable-europe.ec.europa.eu/collection/eupl/li...


yes and that is always true for code

but the situation for artifacts produced from the combinations of code under different licenses is messy in many ways (not just related to this cases)




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: