this post was submitted on 16 Sep 2024
7 points (100.0% liked)

Gaming

2493 readers
320 users here now

The Lemmy.zip Gaming Community

For news, discussions and memes!


Community Rules

This community follows the Lemmy.zip Instance rules, with the inclusion of the following rule:

You can see Lemmy.zip's rules by going to our Code of Conduct.

What to Expect in Our Code of Conduct:


If you enjoy reading legal stuff, you can check it all out at legal.lemmy.zip.


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] taaz@biglemmowski.win 4 points 2 months ago* (last edited 2 months ago) (4 children)

... certain parties violating the old license, by not attributing and stripping my copyright. Packagers being collateral damage was a beneficial side-effect, considering they don't clearly mark their versions as modified (also a GPL requirement), break functionality, and expect upstream to provide support.

Emphasis mine, snipped from the authors comment

As a maintainer of few AUR packages this is always so hurtful.
Where does this position come from? Packaging is the avenue that people using any linux distro use to get your software. This also my first time hearing that packages (re)building GPL code have to mark the packages as modified in some way. I can understand that being a valid concern (if it is one) but that's a problem that can be rather easily fixed without throwing all of the maintainers overboard (?).

I can see there being bad maintainers that will come shouting to upstream with every little thing that does not work on their platform, but man that's just insincere towards maintainers that will dive, analyze and help where they can to make it work.
For every one maintainer coming to your github issues with their problems there is probably shitton of patches and time spent on making your program work with the given distro.

[โ€“] wizardbeard@lemmy.dbzer0.com 6 points 2 months ago* (last edited 2 months ago)

Iirc, the creator of Duckstation has been salty about repackaging his stuff for a good while. He had disagreements with how RetroArch made a core from his emulator, citing some sort of licensing violation (not asure the validity). So someone forked his codebase and made the Swanstation core, and he publicly exploded and ceased development of Duckstation.

He must have come back at some point for his opinions to be relevant again I guess.

As far as I understood things, he's always been touchy about what others chooss to do with his code, even having negative reactions to basic bug fix pull requests.

Apologies if the other response comment covered some of this. I've got them blocked and I'm not going to even try to figure out who on my block list it is and why.

load more comments (3 replies)