>It doesn't matter to me if they change the license but it looks like each source file is >being licensed individually. So unless you are a mamedev you aren't going to know which >all files are used in the emulation of a specific system. Even if you are smart enough >to chase all the includes there are still going to be core files you miss. I think it >has become more murky now.
Like you already mentioned earlier, it used to be one email and that was it. Now it might require searching through all the source files beforehand, seeing which license is used for a specific driver file or associated files which could be two or three variations, and then have to find the author if possible.
Maybe the best current solution might be have each current MAMEdev member place in writing to Micko or MAMEdev website of what can be re-used so that way they don't need to be tracked down later by whoever needs permission to use portions of source code? Granted it is silly because source code is always updated by various contributors over time to each different source file, but I don't know if there is any better solution to resolve this.
In a way, it somewhat reminds me of the National Geographics magazine distributing a cd-rom collection version in late 1990s. The publishing firm had to track down as many contributors and advertisers as possible that provided material for various National Geographics magazine issues over the past century which is a significant undertaking to find: if business (if still existing), or find the rights that were acquired by other business, or find any of the contributors still alive, or their heirs that might retain the copyrights of their deceased relative's work.
The magazine probably gave up and decided to take a gamble through the court system instead.