Aloha,<br><br>first of all, my apologies for writing in HTML, but it seems I can't persuade<br>Gmail to use simple text. Anyone can help? :/<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> 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>The common dirs are easy: docs, which we don't care about, and hash, which<br>
is full of files in MESS but only has one in MAME. I took care of that by<br>
symlinking the single MAME file. :)<br></blockquote><div><br>Ok, I finally sorted this out. :)<br><br>No dir clashes occur on 0.142, but they *did* in 0.141, when I first started<br>working on packaging Mess. I also peeked at the unstable series toward 0.143<br>
and it seems they're patching src/emu/ src/mame/ src/osd/sdl and others.<br>They could also end up as part of the Mame source, but who knows?<br>It's likely that in the future dir clashes can (if not *will*) occur again, and we'd<br>
have to revise the dh_auto_build target. :(<br><br>I also reviewed my own code, which happens to be different from what I recalled ;)<br>* A copy of the (Mame) src/ tree is made to src.Mess/ first,<br>* the makefile and contents of Mess are then copied in src.Mess/<br>
* build is done inside src.Mess/ (and no particular order is required)<br><br>I'd stick with this approach which makes maintainance easier 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">
> 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>Parsing with some grep + regexp hack might help us, but we will always<br>
need to have some manual editing I guess. Geez, thinking about this makes<br>
me sick. :)<br></blockquote><div>...see you in the toilet. I'll already be there... :D<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">
> + 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>
</div><br>I vote for this one! :)<br></blockquote><div>Me too. ;)<br><br>I thought about it and agree that we shouldn't bother, Mame and Mess<br>could eventually share all of them. If not, they're still not so relevant for<br>
the user, after all.<br><br>Anyone else?<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">
> great!<br>
> I'm attaching my full debian dir. It's only ~30k bzipped so I hope it won't</div></blockquote><div> </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">OK, I see there area major differences by now in both trees. Cesare, how<br></div>
do you think we should manage the delta? I'm not sure how ubuntu works,<br></blockquote><div>It's rather simple: we have to choose. :)<br><br>I've just subscribed the list and I don't know about the team inner working.<br>
I understand Jordi and Manu are the team leaders, am I right?<br>
Should I commit my proposals to the repos?<br>Do you prefer to discuss them first?<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;">
but the policy is to prefer not have "ubuntu" changes if possible, right?<br></blockquote><div>Indeed it is.<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;">
Would it work for you if the Ubuntu archive synced our package with, if<br>
necessary, the extra bits you need for a transition? For example, I see<br></blockquote><div>I think we should go exactly in that direction. :)<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;">
you have sdlmame packages for transition that you'd need to keep until a<br>
new Ubuntu release happens, etc.<br></blockquote><div>I'm considering dropping them as transition should be completed for all<br>users after a year or so. ;)<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;">
Also, there's mame-common. Would you mind elaborating what that is for? Is<br>
it to hold those files that both mame and mess can use? (keymaps, etc I<br>
guess?).<br></blockquote><div>Right. It started to ease packaging of other derivatives (namely Wolfmame),<br>as they are not alternatives, strictly speaking. They could even share the<br>same mame.ini as I see no reasons for using different configurations.<br>
We can consider alternatives as well.<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;">think the upstream way of dealing with the mess source code is a bit<br>
horrible. I think mess and mame should simply merge into a single project.<br>
<div><div class="h5">:)<br></div></div></blockquote><div>I agree to both. ;)<br><br>I guess we won't see the merge anyway, for both historical and philosophical<br>reasons. Mame started first, aimed at arcade machines *only*.<br>
Later someone thought about adding home systems, and so Mess was born.<br><br></div></div>Cheers,<br>Cesare.<br>