Hello Jordi, hello all!<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Basically, get-orig-source now fetches the two zips, and converts to a<br>
mame.orig.tar.bz2 and a mame.orig-mess.tar.bz2, being careful to remove<br>
the conflicting files that we mentioned before (the differences are just<br>
line ending).<br></blockquote><br><div>this is my approach too.<br>The source tree is saved in a temp directory for later cleaning, Mame is<br>built first, then incremental source is added and it's Mess turn.<br><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
With this, we would need to again do massive work on debian/copyright<br>
before being ready to reintroduce the mess binary.<br></blockquote><div>unfortunately, yes.<br><br>I've asked the former upstream maintainer of SDLMame, who is member of<br>both Mame and Mess Teams. The claim is, *all* code from both projects<br>
is now released under the Mame licence and copyright is held by the<br>Mame Team for main source and the Mess Team for the additional code.<br><br>We can trust him of course, but peeking at the files things look different.<br>
I guess they are still in the process of updating per-file notes, but I think<br>we should be as much specific as possible in debian/copyright.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> > The package for mess has not been published yet:<br>
> > * it lacks docs and detailed copyright infos<br>
> > * mess-tools shares chdman with mame-tools, I'm stuck between<br>
> > * making mess-tools depend on mame-tool<br>
<br>
</div>Do the tools differ? If so, are they compatible between them? If they are<br>
the same tool, or compatible, I guess the easiest is to handle them via<br>
update-alternatives, with a higher priority for the MAME version.<br></blockquote><div>they are the very same, built from the same source with the same name.<br>Could this be managed with update-alternatives?<br> <br></div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> > * turning both to meta packages and breaking them in a<br>
> > set of packages (mame-chdman, mame-ldplayer,<br>
> > mess-whatever...) which the meta packages will then<br>
> > depend on (recommended IMHO)<br>
<br>
</div>Ugh, this would be way too many packages.<br></blockquote><div>8 more IIRC.<br>If update-alternatives can't do, I'd rather prefer this to "direct"<br>dependecy between *-tools packages, not so neat IMHO.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
</div>Great work! I'm looking forward for you to join the team!<br></blockquote><div><br>
I've (probably... ;) ) managed to register to Alioth and asked for<br>membership in the Debian Games group. This according to Manu<br>should grant me access to the git repository. In the meantime, is it<br>permitted to post my debian/rules file as an attachment to the list?<br>
<br></div>Just to put it right, I'm just a contributor, not a MOTU. I still need<br>sponsorship to upload to the official repository. Difference is subtle,<br>but I don't want to steal any merit from the mentors who spend their<br>
time to revise my package. :)<br></div><br>Cesare.<br><br>