BY: eratosthenes
DATE: 2004-Feb-02 08:12
SUBJECT: RE: The license issueOn the other hand, I do mind it being used as a template for other memory-card based games.
~~~~~~~~~~~~
Option 1
Why not create this very template, by getting mrm to send you his current memory card image, remove the lesschess game from it to leave a "Memcard bootable SPS2 runtime environment", then distribute that image from this site, in the same project as SPS2, with the same license terms?
That way, when you update the SPS2 kernel module and release it in this project, you can simultaneously release an updated memcard image.
This still doesn't allow for the distribution of a memcard image that bundles the game + kernel module together.
Option 2
However, there could be a clever way around this. all you'd need is a single place where the latest version of SPS2 is always available.
Then, create a template Makefile which downloads the latest SPS2, dynamically creates the memcard image, and optionally installs it onto your memcard.
That way, game developers could use this template Makefile, add their own game files, and distribute a working version of the game without actualy redistributing the kernel module themselves.
Option 3
Of course, there's no real reason that a game developer should want to distribute the memcard image. The potential audience for the memcard image is necessarily smaller than the audience for the game in the first place. Game developers should be able to distribute their game, and in their README, or INSTALL, include something like -
"By the way, this game works with the SPS2 bootable memcard image at http://... -"
Summary:
Get mrm to send you his current image
Strip lesschess from that image
Add the image to this site
Reword the SPS2 license to include the image under the same terms as the kernel module itself
If feeling charitable, write instructions on how to use said image with favourite game to amke a memcard bootable version
Comments? |
SPS2UScreenInit() requirements; memcard-linux