Menu

File releases removed, licensing issues

It has come to my attention that MAMEoX has been violating the MAME licensing agreement in at least one or two ways:

1) "The version number must also match the
number of the official MAME version from which you derived your version."
To correct this, the next release of MAMEoX (and the current CVS image) will be versioned either 0.69.1b, or 0.70.1b, depending on how motivated I am to integrate the new core.

2) It appears that placing the readme.txt file in the MAME subdirectory is not enough to "protect" it from the GPL licensing agreement that all original MAMEoX source goes under. We are currently investigating a solution to this problem, and will have more details shortly. It may be possible to explicitely note that the MAME core is _not_ under the GPL, and that most files in the MAME subdirectory are protected under the licensing agreement found in /MAME/docs/mame.txt. If not, I have already provided Sectionize.pl, which automatically modifies the MAME core code to break the drivers up into sections. Some solution (perhaps diff files) will be found to apply the other minor changes that have been made to the MAME core source.

Until this issue is resolved, all file releases have been removed, sorry for the inconvenience. I also apologize for the infractions upon the MAME license, it is not the intention of this project to detract or steal from the official MAME project in any way.

The MAME licensing agreement may be found in the MAME/Docs subdirectory (mame.txt), or on the web at http://www.mame.net/readme.html

Posted by Erik Abair 2003-06-13

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.