http://bugs.winehq.org/show_bug.cgi?id=57797
--- Comment #16 from Richard Yao richard@ryao.dev --- I have built wine and placed the tarball on my HTTPS server for you:
https://ryao.dev/wine-gfn-10.17.tar.xz
The sha256 checksum should be 7773de3cb23ededa0094c4c033386e619ca7d40ad0c7fe9bd4ccdf1890162447.
After patching the wine sources, it was built roughly this way on my Gentoo ~amd64 host (using glibc 2.42):
mkdir build cd build ../configure --prefix=$HOME/my-custom-wine --enable-archs=i386,x86_64 make -j$(nproc) make install DESTDIR=/tmp/wine -j$(nproc)
I used DESTDIR to verify that nothing was installed outside of the prefix, which was the case. Then I renamed my-custom-wine to wine-gfn-10.17, made a sources directory inside it and placed a copy of the sources used to build it there. I made a tarball like this:
cd /tmp/wine/home/richard tar -vcf wine-gfn-10.17.tar wine-gfn-10.17/ xz -9e wine-gfn-10.17.tar
Also, I did some basic tests on the result by doing the following and verifying that the application ran without crashing:
env WINEPREFIX=~/test-prefix /tmp/wine/home/richard/wine-gfn-10.17/bin/wineboot -i env WINEPREFIX=~/test-prefix /tmp/wine/home/richard/wine-gfn-10.17/bin/wine Downloads/GeForceNOW-release.exe env WINEPREFIX=~/test-prefix /tmp/wine/home/richard/wine-gfn-10.17/bin/wineserver -k
Although I cannot guarantee indefinite availability on github, a copy of the sources is also available there in the nvidia-10.17 development branch at commit d6de1cfeea99385ffd6156e6facaa464ef5ed0aa:
https://github.com/aabgrall/wine-base-geforcenow
If I ever take down the tarball and the github repository ceases to operate, I will be unable to satisfy requests for sources under the LGPL, but my obligation to provide sources is implicitly fulfilled by bundling them in the tarball, so I wash my hands of any further obligations to provide sources.
I am probably being pedantic, but ensuring source code availability is legally required by the LGPL whenever anyone provides binaries across organizational boundaries. I do not like unbound legal obligations, which is why I almost never provide GPL/LGPL binaries and usually insist on providing source code to others. If I could not circumvent the LGPL/GPL requirements by bundling the sources, I would not have done this.
Finally, I should reiterate that you should never trust binaries built by random people on the internet. You should always insist on building from source yourself rather than implicitly trusting others who provide binaries. In the cases where you do trust people who provide binaries, they should always be from well trusted sources such as distributions, rather than random individuals. I usually never provide binaries to others for the above reasons, and I am only doing this so that you can verify that the patch works in your VM environment.