As I posted below, this isn't a problem because MAME itself is not being relicensed and will continue to be distributed under the current license for the forseeable future.
Hence, every file in MAME with a tag for non-MAME licenses implicitly becomes multiply licensed as MAME+the other licenses, and a deco16 like conglomeration then gets licensed as the set of licenses that appear in all of the original component files, which will always be at least the MAME license. Combining MAME+BSD and MAME+LGPL source files the combination can legally be licensed just MAME, for instance.
Of course, it's a good idea to contact the original authors where possible in this kind of case.
|
Index 
Flat 
Re: The Multiple License Conundrum
Reply
