> Are we talking about just releasing "diff" patches where one has to run > patch or already patched files in a tarball that just get unpacked over > the top of the mame source package?
Neither, I was thinking more about things like // to /* */ conversion, which are not specific to a particular version. The only thing I know of that could cause a bit of a problem are variables declared in a block, you could automate it but it's a major amount of work. They seem to creep in every so often because everyone else seems to use a compiler that allows them. AFAIK patches for them are accepted & Lawrence could find them before the release occurs, but I guess he doesn't have the time. When I had problems like this with dos mame I included the entire file & made sure it got fixed for the next release. As long as you tell people how to extract only newer files then you should be ok. Haze is much more likely to accept patches for xmame specific issues than Nicola was, so if there is something that would improve the portability of the main source then it should be submitted ( unfortunately I think it's unlikely that you'll see a switch to /* */ though ). Phill _______________________________________________ Xmame mailing list [EMAIL PROTECTED] http://toybox.twisted.org.uk/mailman/listinfo/xmame
