This article is from the WINE WINdows Emulator FAQ, by Dave Gardner firstname.lastname@example.org with numerous contributions by others.
Because of lags created by using mirror, word of this newest release may
reach you before the release is actually available at the ftp sites listed
here. The sources are available from the following locations:
It should also be available from any site that mirrors tsx-11 or sunsite.
Some of these ftp sites may archive previous versions of Wine as well as
the current one. To determine which is the latest one, look at the
distribution filename, which will take the form Wine-[yymmdd].tar.gz.
Simply replace [yymmdd] in the distribution filename with the numbers for
year, month and date, respectively. The latest one is the one to get.
Wine is also available in RedHat and Debian packaged versions, but the
packaging delays the release in these formats for about a week after the
*.tar.gz file is released. You can obtain these packages from the following
Compiled binaries for the Solaris operating system can be found at:
Current Wine sources are also available via anonymous client/server CVS.
You will need CVS 1.9 or above. If you are coming from behind a firewall,
you will either need a hole in the firewall for the CVS port (2401) or use
SOCKS. To login to the CVS tree, do
Use "cvs" as the password (without the quotes). Note that /home/wine is
a path on the server, not on your machine.
To check out the entire Wine source tree (which may be slow), use:
cvs -z 3 checkout wine
or if you just want a subtree, or individual file, you can do that too
cvs -z 3 checkout wine/ANNOUNCE
Be aware, though, that getting the entire Wine source tree via CVS is
pretty slow, especially compared to getting Wine from an FTP mirror near
Patch files are also available, so that you don't have to download,
install and configure the entire distribution each week if you are current
to the previous release. Patch file release names follow the same
numbering convention as do the general releases, and take the form:
Patch files are available from the same sites that distribute the full
release. To upgrade to a new release by using a patch file, first cd to
the top-level directory of the release (the one containing the README
file), then do a "make clean", and patch the release with:
gunzip -c patch-file | patch -p1
where "patch-file" is the name of the patch file (something like
Wine-yymmdd.diff.gz). You can then re-run "./configure", and then
run "make depend; make".
Note that any mirror of tsx-11 will likely carry the Wine distribution and
diff files, but may not be listed here in this FAQ.
If you are mirroring the Wine distribution from the tsx-11 site and wish
to be listed here in this FAQ, please send email to the FAQ
author/maintainer listed in question 7.2.