1 |
%define PYTHON_NAME %((rpm -q --quiet python2 && echo python2) || echo python) |
2 |
|
3 |
Version: $version |
4 |
Summary: Convenient and transparent local/remote incremental mirror/backup |
5 |
Name: rdiff-backup |
6 |
Release: 0.fdr.3 |
7 |
Epoch: 0 |
8 |
URL: http://rdiff-backup.stanford.edu/ |
9 |
Source: http://rdiff-backup.stanford.edu/OLD/%{version}/%{name}-%{version}.tar.gz |
10 |
License: GPL |
11 |
Group: Applications/Archiving |
12 |
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) |
13 |
Requires: librsync >= 0.9.6, %{PYTHON_NAME} >= 2.2 |
14 |
BuildPrereq: %{PYTHON_NAME}-devel >= 2.2, librsync-devel >= 0.9.6 |
15 |
|
16 |
%description |
17 |
rdiff-backup is a script, written in Python, that backs up one |
18 |
directory to another and is intended to be run periodically (nightly |
19 |
from cron for instance). The target directory ends up a copy of the |
20 |
source directory, but extra reverse diffs are stored in the target |
21 |
directory, so you can still recover files lost some time ago. The idea |
22 |
is to combine the best features of a mirror and an incremental |
23 |
backup. rdiff-backup can also operate in a bandwidth efficient manner |
24 |
over a pipe, like rsync. Thus you can use rdiff-backup and ssh to |
25 |
securely back a hard drive up to a remote location, and only the |
26 |
differences from the previous backup will be transmitted. |
27 |
|
28 |
%prep |
29 |
%setup -q |
30 |
|
31 |
%build |
32 |
%{PYTHON_NAME} setup.py build |
33 |
|
34 |
%install |
35 |
%{PYTHON_NAME} setup.py install --prefix=$RPM_BUILD_ROOT/usr |
36 |
|
37 |
%clean |
38 |
[ "$RPM_BUILD_ROOT" != "/" ] && rm -rf $RPM_BUILD_ROOT |
39 |
|
40 |
%files |
41 |
%defattr(-,root,root) |
42 |
%{_bindir}/rdiff-backup |
43 |
%{_mandir}/man1/rdiff-backup* |
44 |
%{_libdir}/ |
45 |
%doc CHANGELOG COPYING FAQ.html README |
46 |
|
47 |
%changelog |
48 |
* Thu Aug 8 2003 Ben Escoto <bescoto@stanford.edu> |
49 |
- Set librsync >= 0.9.6, because rsync.h renamed to librsync.h |
50 |
|
51 |
* Sun Jul 20 2003 Ben Escoto <bescoto@stanford.edu> |
52 |
- Minor changes to comply with Fedora standards. |
53 |
|
54 |
* Sun Jan 19 2002 Troels Arvin <troels@arvin.dk> |
55 |
- Builds, no matter if Python 2.2 is called python2-2.2 or python-2.2. |
56 |
|
57 |
* Sun Nov 4 2001 Ben Escoto <bescoto@stanford.edu> |
58 |
- Initial RPM |