https://bugs.winehq.org/show_bug.cgi?id=45391
--- Comment #2 from Forest forestcode@ixio.org --- Thanks, Michael. Yours is the first constructive response I've found from anyone, after weeks or months of multiple people asking about this problem.
With respect to the license and the intent of the LGPL, it seems worth pointing out that reproducing binary packages requires more than access to wine's git repo. At the very least, it requires knowing exactly what build configuration options were used, and what wine changeset was checked out for the build. In the vast majority of binary packages that I've seen, there are quite a few additional components involved, including patches, install scripts, distribution-specific dependencies, and the like. I don't fancy myself an expert in how the LGPL is interpreted, but from a purely task-oriented perspective, all of these things are parts of the source code for a binary package, yet none of them have been made known to the people to whom the binaries are being distributed.