3 ms·
If I were running the project, I'd put a very firm comment like this: @Maniues: Please explicitly list all files in this project that violate GPL, or I will cl
by gwbas1c 5y ago
If I were running the project, I'd put a very firm comment like this:
@Maniues: Please explicitly list all files in this project that violate GPL, or I will close this issue by (Some reasonable date.)
Then, by that date, I'd double-check that none of the code violates the GPL.
Why: I suspect that Maniues has a poor understanding of the semantics needed to determine if the project actually violated the GPL. It's quite common for people to raise a ruckus on something that they don't understand.
Upon closing the issue, I'd state, "I checked all of our dependencies, including XXX. Nothing violates the GPL." If there's LGPL or similar, I'd say something like, "We use XXX, which is LGPL, not GPL, and we are in compliance with the license."
Then I would close the issue. Issues like this shouldn't be left unresolved.
- cyberbanjo 5y ago> all files in this project that violate GPL This comment is in a different issue, not sure if it's exactly that: https://github.com/cheat-engine/cheat-engine/issues/60#issuecomment-942071225 https://github.com/cheat-engine/cheat-engine/issues/60#issue...
- gwbas1c 5y ago"Go read XXX" is a non answer. (The link also doesn't list the files in violation.)