Hello again Jordi and 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">As I haven't tried a mess build yet, I don't know why this is needed. Why<br>
do you need to build mame first, then mess? Can't you setup the build at<br>
the beginning and build both at the same time? Wouldn't that just create<br>
two different binaries?<br></blockquote><div>the source tree in Mess tarball has some directories in common with Mame.<br>I don't remember whether overwrites occur (I had to halt the Mess thing for<br>a while due to lack of time), btw I chose to make it short and build them in<br>
turn.
I'll have a closer look when I'm back home.<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">The problem with this detailed handling of debian/copyright is the pain in<br>
the ass it is to maintain properly. Right now, Manu is doing an awesome<br>
job registering the new files, but are we checking changes to already<br>
registered files? Are we removing files that get removed from the<br>
distribution? If we don't find a way to make this easier to maintain,<br>
it'll be a nightmare... :/<br></blockquote><div>don't tell me. :o<br>It nearly drove me crazy during this years, and I must admit I probably<br>missed something at some point.<br>I thought about it a lot, we can take for granted what the Mame/Mess team<br>
say or we can write some kind of parsing tool. I see no other ways. :(<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>Yes, or maybe even a diversion, but probably an alternative is the optimal<br></div>
way. It's silly, because it means providing an alternative for the very<br>
same thing. Or, another proposal, just stick mess tools in mame-tools and<br>
make it provide mess-tools. Are there many new tools in mess?<br></blockquote><div>at present there are 2, plus the one related to both.<br><br>Should we chose to make a single mame-tools package, I'd see no need<br>
for providing mess-tools, as it doesn't really exist yet. ;)<br>We could just making mess suggest mame-tools, couldn't we?<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><br>
> 8 more IIRC. If update-alternatives can't do, I'd rather prefer this to<br>
> "direct" dependecy between *-tools packages, not so neat IMHO.<br>
<br>
</div>Given they are so closely related, I'd prefer the "one package for both"<br>
thing, but I admit I've never come across this situation.<br></blockquote><div>Yeah, I think it's a really peculiar one.<br><br>Let's sum up:<br>* there's a number of tools provided, only one related to both Mame<br>
and Mess but we can't be sure they won't be more in the future<br>* we have collected many thoughts on how to manage this so far:<br> + using alternatives, mess-tools depends on mame tools<br> - pros: tools are clearly linked to the corresponding emulator<br>
- cons: the same binary (could be more) repeated; silly way to use<br> alternatives; a mess (no pun intended ;) ), should a mess tool<br> become related to mame too<br> + mess-tools and mame-tools are meta-packages, depending on<br>
multiple packages, one for each tool<br> - pros: the same as above<br> - cons: lots of binary packages<br> + all tools are in a single mame-tools package<br> - pros: probably easier to maintain in the future; no redundancy<br>
- cons: the user can't tell which is which anymore<br><br>I'm uncertain. I guess I still need some thinking on this. ;)<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><br>
> I've (probably... ;) ) managed to register to Alioth and asked for<br>
> membership in the Debian Games group. This according to Manu should<br>
> grant me access to the git repository. In the meantime, is it permitted<br>
> to post my debian/rules file as an attachment to the list?<br>
<br>
</div>Absolutely! I have pushed my stashed changes to the repo, but you're free<br>
to improve it if needed.<br></blockquote><div>great!<br>I'm attaching my full debian dir. It's only ~30k bzipped so I hope it won't hurt<br>anyone. Please note the contrib files. I submitted the man pages upstream,<br>
but they're not been included in the main tree AFAIK.<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>
Now, my idea is to setup a few symlinks to make mess appear in the mame<br>
usual tree so it can get compiled. Dunno if Cesare had another idea or<br>
approach.<br></blockquote><div>I did something different (see above), but your idea could be better than mine.<br>We need to check whether file/dir clashing occurs first. ;)<br></div><br>
</div>Cheers!<br>Cesare.<br><br>