<h2 align="center">rsync download</h2>
-<h2>Source Code</h2>
+<h2>Source-code releases (tar files)</h2>
<p>You can grab the latest source code tar file, its gpg signature, and other
related files in a variety of ways:
</ul>
<p>Also, an unpacked copy of the latest development version can be
-<a href="/ftp/unpacked/rsync/">browsed on the web</a>, or obtained via
-<i>anonymous rsync</i> from:
-<code><small>rsync://rsync.samba.org/ftp/unpacked/rsync/</small></code>
+<a href="/ftp/unpacked/rsync/">browsed on the web</a> or obtained via
+<i>anonymous rsync</i>, as described in the Source Repository section.
+
+<h2>The GPG Signing Key</h2>
+
+The GPG signing key that is used to sign the release files and the postings to
+the rsync-announce mailing list is available from the public pgp key-server
+network. If you have automatic key-fetching enabled, just running a normal
+"gpg --verify" will grab my key automatically.
+Or, feel free to grab <a href="http://opencoder.net/WayneDavison.key">the gpp
+key for Wayne Davison</a> manually.
<h2>Binaries</h2>
<p>Precompiled binaries are available in most modern OS distributions, so
-you might want to first check if you can install an rsync package via your
+you should first check if you can install an rsync package via your
standard package-install tools for your OS.
<p>There are also packages available from some <b>3rd-parties</b> (note that we cannot
<li><p><a href="http://dag.wieers.com/packages/rsync/">RPMs for Red Hat/Fedora</a> from Dag Wieers.
-<li><p><a href="http://www.kepreon.com/~matt/myrsync/">RPMs patched with ACL support</a> from Matt McCutchen.
+<li><p><a href="http://mattmccutchen.net/rsync/#rsync-packages">RPMs packages for i386 linux</a> from Matt McCutchen.
<li><p><a href="http://sunfreeware.com">Packages for SPARC/Solaris 2.5-10 and x86/Solaris 8-10</a>.
<li><p><a href="http://itefix.no/cwrsync/">cwRsync</a> is a packaging of rsync for MS Windows.
-<li><p>More to come...
-
</ul>
-<h2>CVS</h2>
+<h2>Nightly tar-file snapshots</h2>
+
+<p><a href="/ftp/rsync/nightly/">Nightly snapshots of the
+rsync source tree</a> are also available for people who want to try the latest
+development version. If you want to track development, then using an anonymous
+rsync copy will not require as much bandwidth (see below). Or, updating a git
+repository can automatically merge your local changes with our version.
+However, one thing the tar file has going for it is that it contains several
+generated files that are not present in the source repository (such as
+configure.sh, config.h.in, etc.). It can also be helpful if you cannot use
+rsync or git because of firewall, network, or software issues.
+
+<h2>Source repository</h2>
<p> The rsync development tree is publicly available by various methods so that
you can try out the latest changes and give feedback to the developers.
-<p> <b>Note:</b> Since the "HEAD" source is a work in progress it may not
-compile, or may fail in various ways, though it's usually pretty good.
+<p> <b>Note:</b> Since the source repository is a work in progress it may, at
+times, not compile or fail in various ways, though it is usually pretty good.
-<p> Anyone may use anonymous CVS to follow development:
+<p>Anyone can browse the development history through
+<a href="http://gitweb.samba.org/?p=rsync.git">gitweb</a>.
-<blockquote>
-<p><code>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login</code>
-<p> <i>(Specify the password <b>cvs</b> when prompted.)</i>
-<p><code>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot co rsync</code>
-</blockquote>
+<p>You may also use the git version-control system to check out the latest
+development version, especially if you want to make local changes. The
+following command will check-out the latest version into a directory named
+"rsync":
-<p>You can also browse the <a href="http://cvs.samba.org/cgi-bin/cvsweb/rsync">development
-history through cvsweb</a>.
+<blockquote><pre>git clone git://git.samba.org/rsync.git</pre></blockquote>
-<h2>Nightly CVS Snapshots</h2>
+<p>After the initial clone, I also recommend running the git-set-file-times
+script to set each file's last-modified time based on its last commit (don't
+run it again after that unless you do a "make distclean"). You'll also need
+autoconf and autoheader installed for the "prepare-source" command to succeed
+unless you use either the "fetch" or "fetchall" option (these options can only
+fetch the most recent generated file that goes with the latest git version):
-<p><a href="http://rsync.samba.org/ftp/rsync/nightly/">Nightly snapshots of the
-rsync source tree</a> are also available for people who want to try the latest
-development version. If you want to track development, then CVS uses less
-bandwidth and can automatically merge your local changes with our version.
-However, if you just want a one-off download, or cannot use CVS because of
-firewall, network or software issues, then the snapshots might be helpful.
+<blockquote><pre>cd rsync
+support/git-set-file-times # optional
+./prepare-source</pre></blockquote>
+
+<p>
+
+<p>Updating your git checkout with the latest source is very easy:
+
+<blockquote><pre>git pull</pre></blockquote>
+
+<p>Those wanting to just obtain the latest source without the entire git
+repository can either use a nightly tar-file snapshot (see above)
+or use an <i>anonymous rsync</i> copy of the unpacked source files:
+
+<blockquote><pre>rsync -av --exclude=.git/ rsync://rsync.samba.org/ftp/unpacked/rsync /dest/dir/</pre></blockquote>
+
+<h2>Source repository patches</h2>
+
+<p>There are also various patch files in the "rsync-patches.git" repository that
+represent either some work-in-progress features or features that are considered
+to be a little too fringe-interest for the main release. You can use
+gitweb to <a href="http://gitweb.samba.org/?p=rsync-patches.git">browse the
+latest patches</a>. Each branch in the patches repository matches the branch
+of the same name in the <a href="http://gitweb.samba.org/?p=rsync.git">main
+repository</a>, so "master" matches "master", and "b3.0.x" matches "b3.0.x".
+
+<p>Use the
+<a href="http://gitweb.samba.org/?p=rsync-patches.git;a=tree;h=refs/heads/master;hb=master">tree
+view of the master branch</a> or the
+<a href="http://gitweb.samba.org/?p=rsync-patches.git;a=tree;h=refs/heads/b3.0.x;hb=refs/heads/b3.0.x">tree
+view of the b3.0.x branch</a> to get to the contents of individual files (i.e. click
+on the "raw" link for the file you want).
+
+<p>Each release of rsync also has an associated sync-patches-VERSION.tar.gz
+file with the patches as they existed at the time of the release.
<!--#include virtual="footer.html" -->
git.samba.org / rsync-web.git / blobdiff