> I am not sure how you talk about the whole team. Maybe you CAN talk about the whole
> team, I don't know. I think there are different voices though.
I'm just reporting the opinion of the majority of the devs as it emerges from the opinion given on the dev list. no more, no less. since we generally proceed by democratic discussions, that becomes the current position of the team.
> The problem is EXACTLY for people NOT capable of compiling a combined exe; which btw
> traditionally face some discrimination in some open source projects. In those
> projects (and I am not saying MAME is one of those) it is very common to face an
> almost racist comment "if you want it like that, do it yourself"... well having been
> on both sides in different phases of my IT life, I don't like that reply.
>
> The problem also is that the way to build the combined exe is not (YET) official.
> Why? The best (? AFAIK) effort right now comes from a member that (again AFAIK)
> doesn't have the sympathy of some of the members of the team (for reasons we frankly
> do not care). This to an outsider (like me) seems like politics and just politics.
no offense, but reasons have been explained many times and if you still think there is politics involved, maybe you shall check these forums as often as you check Haze's blog. 
for one, at the moment MAMETesters is not ready to take care of MESS bugs too, so a merging of the exes would harm our best bug tracking resource; for another, current MESS svn is public, while the MAME one is not and there are bandwidth concerns about making the latter public (closing the former is not an option, of course)...
the situation might change in future, but I think for the moment we can ship separate exes with no harm
|
Index 
Flat 
Re: Combined build
Reply
