If you don’t want to see your software packaged in ways outside of your control, is it smart to publish it with a license that allows it to be packaged in ways outside of your control?
If you don’t want to see your software packaged in ways outside of your control, is it smart to publish it with a license that allows it to be packaged in ways outside of your control?
JackbyDev@programming.dev 4 weeks ago
~11 months ago they relicensed from GPL 3 to CC BY-NC-ND.
bss03@infosec.pub 3 weeks ago
Oh. Time for a fork. -ND variants are not Free Software / Open Source.
JackbyDev@programming.dev 3 weeks ago
Having read a lot of the thread it sounds like that’s sort of what’s going on with the version on the AUR. Sounds like it is the old GPL v3 version and the dev doesn’t wanna put the new CC BY-NC-ND version on the AUR themselves because they don’t want to make an account there (understandable, not saying they should have to).
The whole situation is sort of sad, but ultimately devs working on free (as in money, I now -ND is not libre) software need to do what they need to do to remain sane. If it’s a CC BY-NC-ND emulator without Linux support versus no emulator at all I think we’d all want the first.
I hope this thread can be an eye opener for folks to remember to treat volunteer devs with respect. (Not implying anyone here was part of the problem.)
Wispy2891@lemmy.world 3 weeks ago
No, on aur there’s
duckstationwhich is the old GPL3 version (stuck to one year ago) andduckstation-gitwhich downloads that git with latest license and compiles on the end user machine. Both versions respect the dev intentions of “no packages” as it downloads the code and compiles it. The problem that it was about were probably twoDocumentation on how to compile is insufficient. It depends on many libraries but doesn’t say which exact version which causes issues at compile. Someone did the guesswork and wrote “instructions” (the pkgbuild file) for everyone but it’s not the main dev and it breaks often
Because it downloads the code from git, it might be an issue if it’s not tagged correctly, users get the latest commit instead of latest release and that’s undesirable (didn’t check for this case, but it was an issue for other emulators where non devs could run buggy code and complain about non-issues)