Is there a reason for Ludo and Manu not working on getting MESS in Debian
at the same time as MAME before I got involved in this effort? I'm
interested in helping getting this done as we've done with MAME, but will
not do it if I won't be able to count with the help of the rest of the
people in this list.
So, just wondering what happened. :)
Jordi
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/
Well it used to be that the MESS legalese was not so clear, disallowing
distribution of modified binaries. But now they settled rightly on the
same license as Mame http://mess.redump.net/license
The MESS source code is a layer of files over the Mame source code.
( extract from http://mess.redump.net/downloads )
Note that you need to get the MAME sources as well if you want to
compile MESS - to save space, the MESS source is just an overlay that is
meant to be extracted on top of the MAME source of the same version,
which contains e.g. the makefile. (This is not necessary if you pull
from SVN, which includes the MAME source.)
So a first easy step would be to change the get-orig-source target to a
svn checkout so Mame would be built from the Mame + Mess source code.
For myself the learning curse for Debian Packaging has been steep enough
that I am not going to start working on extra packaging right now ( I've
just understood quilt and I am not yet with cowbuilder and
git-buildpackage :)
Manu
I'm the maintainer of Mame in Ubuntu, and I'm willing to share efforts
and knowledge to improve support both in Debian e Ubuntu.
I'm currently working (slowly...) on Mess too, so I guess it's the right
place where I might help. ;)
> The MESS source code is a layer of files over the Mame source code.
> ( extract from http://mess.redump.net/downloads )
>
> Note that you need to get the MAME sources as well if you want to
> compile MESS - to save space, the MESS source is just an overlay that is
> meant to be extracted on top of the MAME source of the same version,
> which contains e.g. the makefile. (This is not necessary if you pull
> from SVN, which includes the MAME source.)
>
> So a first easy step would be to change the get-orig-source target to a
> svn checkout so Mame would be built from the Mame + Mess source code.
I'm taking advantage of the multiple tarball feature of debsource 3.0
instead. I think this is more solid than pulling from SVN.
There's also a bad issue: Mess comes with a couple of tools, and shares
chdman with Mame. So I'm stuck choosing between making mess-tools
depending on mame-tools and breaking mame-tools in a set of different
packages (mame-chdman, mame-ldplayer etc.) and turning it into a
meta-package depending on them (and of course making the same thing with
mess-tools).
Any suggestions?
Cesare.