BY: eratosthenes
DATE: 2004-Feb-03 06:43
SUBJECT: RE: The license issueIt's not my license, it's Sauce's :)
Anyway, talking with Sauce last night on IRC he seems alright with the idea of such images. I'm expecting himt o give you permission so send that image out any day now.
In the meantime of course, you could send me the image with the kernel module deleted, and tell me where to drop the kernel module back into.
SPS2 license background:
To give a brief bit of background, the aim of the license is to prevent multiple copies of the kernel module being installed on any one machine. At the moment, your compiled kernel module, using the latest version of SPS2, is bit for bit the same as mine. This might not necessarily be true in the future.
If game developers were allowed to distribute the kernel module, they'd most likely dump it over the top of whatever module you already had there. This may break your configuration.
So, the aim of the license is to make user's life easier, they are responsible for installing the kernel module on their system, where they want it, and no game developer is licensed to muck that up.
In this particular case, you're not overwriting an existing sps2 kernel module, you're creating an entrie filesystem, so there's no possibility of multiple sps2 kernel modules appearing all over the hard drive.
So, memcard image = OK, multiple sps2 kernel modules all over hard drive = Not OK. Thing is, this is really diffcult to word into a license. |
SPS2UScreenInit() requirements; memcard-linux