You can’t fork it or redistribute it… but you can distribute patches for users to apply, and those are easy to add in a PKGBUILD. That’s how a lot of game/ROM patches are distributed and they appear to be legal.
It’s an emulator, lets be real, the majority of the users couldn’t give a shit about license terms anyway.
Yeah… But then it sucks for anyone not running Arch (btw) or derivative distros. I really don’t have a dog in this merge conflict but really would feel bad for any packager maintainers.
but really would feel bad for any packager maintainers.
It’s already unpackageable because of the license anyway.
The only “legit” way to get the emulator is their provided AppImage bundle, and nothing else. The author also has a rant about Flatpak being broken and unreliable and refusing to support that, so…
I have some issues with flatpak, myself, but that mainly stems from having trouble finding documentation to clear up how to properly use extensions and non-standard dependencies that are easy to do with OCI images.
Ex. I had a really hard time trying to get Vega Strike built as a flatpak.
Yeah im sure someone will fork and it will be named chickensation or whatever. Then we will move on.
Hope the developer feels better. Its easy to get burnt out on passion projects. If I were to guess, this is what is happening. They are going to say some pretty insane things in the next couple of weeks and then get a handle on their life.
Ive always liked: epsxe myself. Works well and no real drama. Its a very old console.
Just fork it lol
This is the dev that changed the license a while back from GPL to CC-BY-NC-ND because they got mad about forks.
The kicker here is that the AUR package they’re whining about here is based on the last GPL version.
So he fucked his own packaging with the licenses and now blames the users for complaining? Common Windows Dev L
oof. Good luck with that in FOSS world.
I can sympathize with being frustrated but that’s silly
Eh. PCSX core ain’t broke. Whatever. I’ll live.
I suggest using Beetle mednafen, unless you’re on a very slow system. Or Swanstation, it’s not like that’s going away.
PCSX is a lot less accurate.
So couldn’t someone just fork from the version on AUR?
It doesn’t matter what he does, because any project on GitHub can be forked, and it’s in their TOS.
By creating a project there, he agreed to that TOS, so he can’t disallow forks, simple as that.
Would have to go back to before the license change in September 2024. The current license basically forbids forks, from my reading.
You can’t fork it or redistribute it… but you can distribute patches for users to apply, and those are easy to add in a PKGBUILD. That’s how a lot of game/ROM patches are distributed and they appear to be legal.
It’s an emulator, lets be real, the majority of the users couldn’t give a shit about license terms anyway.
It’s also a PS1 emulator. A console that’s been emulated for over 20 years now.
Getting flashbacks to installing qmail back in the day…
I have a heard time imagining it to be worth it with other psx emulators readily available without weird hoops to go through.
Yeah… But then it sucks for anyone not running Arch (btw) or derivative distros. I really don’t have a dog in this merge conflict but really would feel bad for any packager maintainers.
It’s already unpackageable because of the license anyway.
The only “legit” way to get the emulator is their provided AppImage bundle, and nothing else. The author also has a rant about Flatpak being broken and unreliable and refusing to support that, so…
I have some issues with flatpak, myself, but that mainly stems from having trouble finding documentation to clear up how to properly use extensions and non-standard dependencies that are easy to do with OCI images.
Ex. I had a really hard time trying to get Vega Strike built as a flatpak.
If it’s only available via appimage, as the reply to this comment states, then it will still run just fine on Arch.
Yeah… That’s pretty terrible. I was meaning packaging patchsets for other distros. Hopefully the GPL-preserving fork is better.
Why is it terrible? Appimages are fine.
Appinages are fine. Needing to apply changes as patchsets rather than just building normally sucks. Especially in deb and rpm distros.
Yeah im sure someone will fork and it will be named chickensation or whatever. Then we will move on.
Hope the developer feels better. Its easy to get burnt out on passion projects. If I were to guess, this is what is happening. They are going to say some pretty insane things in the next couple of weeks and then get a handle on their life.
Ive always liked: epsxe myself. Works well and no real drama. Its a very old console.
https://github.com/libretro/swanstation