MAMEWorld Forums - Programming - What is the policy on distributing patches?

Hello. I have a patch against MAME that I would like to make public and would like to distribute binaries based on the patch for user convenience.

What is the general policy for this?

The MAME license says that the "complete source code" for the modified version of MAME must be included. Does this mean that posting the patch is not sufficient if I want to post binaries and that I have to post the fully patched MAME source as well?

In any case, is it sufficient to put a link to the source on the site that distributes the binaries or do I have to package the binaries in a way that implicity includes the source - such as together in a .zip file?

Also the MAME license includes "the source code for all components used by a binary built from the modified sources" in this requirement.

Does that mean that if the MAME code is built into a shared library (.so or .dll), these license requirements for the programs that link against MAME are included?

I guess the two questions I am asking can be boiled down to this:

1. What does the term "redistribution" mean as MAME uses it in its license in the sentence fragment:

"Redistributions that are modified from the original source must ..."?

Does "redistribution" include "distribution of a binary that links against a shared library that includes MAME code"? If so, how does that work, because the binary itself doesn't contain any MAME code, it just contains code which has symbol dependencies on code that could be satisfied by MAME or could be satisfied by some other library that defines the same symbols ...

2. What does the term "include" mean as MAME uses it in its license in the sentence fragment:

" ... include the complete source code ..."

Does it mean making the source available from the same medium as the binary, but not necessarily implicitly included along with the binary? Or does it mean implicitly included along with the binary?