INSTALLATION:

Thank you for trying rdiff-backup.  To install, run:

	python setup.py install

The build process can be also be run separately:

	python setup.py build

The default prefix is /usr, so files are put in /usr/bin,
/usr/share/man/, etc.  An alternate prefix can be specified using the
--prefix=<prefix> option.  For example:

	python setup.py install --prefix=/usr/local

The setup script expects to find librsync headers and libraries in the
default location, usually /usr/include and /usr/lib.  If you want the
setup script to check different locations, use the --librsync-dir
switch or the LIBRSYNC_DIR environment variable.  For instance,

	python setup.py --librsync-dir=/usr/local build

instructs the setup program to look in /usr/local/include and
/usr/local/lib for the librsync files.

Finally, the --lflags and --libs options, and the LFLAGS and LIBS
environment variables are also recognized.  Running setup.py with no
arguments will display some help.


REQUIREMENTS:

Remember that you must have Python 2.2 or later and librsync 0.9.7 or
later installed.  For Python, see http://www.python.org.  The
rdiff-backup homepage at http://www.nongnu.org/rdiff-backup/ should
have a recent version of librsync; otherwise see the librsync homepage
at http://librsync.sourceforge.net/.

For remote operation, rdiff-backup should be in installed and in the
PATH on remote system(s) (see man page for more information).

The python modules pylibacl and pyxattr are optional.  If they are
installed and in the default pythonpath, rdiff-backup will support
access control lists and user extended attributes, provided the file
system(s) also support these features.  Pylibacl and pxattr can be
downloaded from http://pylibacl.sourceforge.net/ and
http://pyxattr.sourceforge.net/.


TROUBLESHOOTING:

If you have everything installed properly, and it still doesn't work,
see the enclosed FAQ.html, the web page at
http://www.nongnu.org/rdiff-backup/, and/or the mailing list.

