>If stuff gets mislicensed, it's quite obvious How-so? I would think the opposite, unless every contributor remembers every line they ever wrote there's no way to know with much degree of certainty.
>A MAME+BSD file combined with a MAME+LGPL file would end up MAME-only In which case the whole change is moot is it not? If parts of MAME are restrictively licensed then how is anyone without intimate knowledge of the code base going to know if their usage is in violation or not? Certainly, some museum curator can't just download MAME and use it on the assumption that it is using an OSI-approved license.
Don't get me wrong, the current MAME license is a bad idea for all the reasons you point out but changing it at this point is going to either be extremely messy and likely incomplete or just gloss over stuff in the hopes no one complains.