New Branch for building Mame and Mess >= 0.144

[Emmanuel Kasper]

Hello Cesare !
>> Hrm. Upstream's opinion is important, and we don't want to piss him off.
>> On the other hand, the huge code duplication is no fun, and the security
>> team wouldn't be happy either.
> I'm sorry, I still haven't looked at the recent changes, I hope I will in the
> next few days.
> 
> I tend to agree with Arbee, however. No matter the amount of code duplication
> we must deal with. The proper way to build a package is to build it from the
> upstream source IMO.

Hum, after a lot of thinking again I think yes, we should track the two
repositories separately. It is not like we are shipping old libraries in
the package.
So I am thinking of  creating a git repo on alioth for mess, and let us
see how thing evolves in upstream. If we have a separate package for
mess, it means also it will be in ubuntu automatically in Ubuntu by the
next unstable thing.
For the tools I will check what is built in mess "TOOLS" target I guess
he buils the mame tool as well.

> 
> I've lately discovered that png files in artwork/ should be distributed as mask
> images for the -effect switch, I'll commit the modified mame.install file ASAP.

Nice ! I was wondering what were these files for,please go ahead.

Manu