rdiff-backup and rdiff-backup-devel.
- Remove rdiff-backup-devel and add an entry to MOVED to migrate users to
rdiff-backup.
- Add an UPDATING to notify users about the incompatibility between the
last version of rdiff-backup and version 1.0.1
PR: ports/86108
Submitted by: Vasil Dimov <vd@datamax.bg>
Approved by: Steve Clement <steve@ion.lu> (maintainer, rdiff-backup)
Peter Schuller <peter.schuller@infidyne.com> (maintainer, rdiff-backup-devel)
Discussed with: submitter and a couple of other rdiff-backup users
incorrectly submitted to the latest stable version.
- Add a pkg-message explaining incompatibility between this and
the last version.
- Remove a patch no longer needed
PR: ports/80079
Submitted by: Steve Clement <steve@fucker.ion.lu>
Approved by: clement (mentor)
rdiff-backup backs up one directory to another, possibly over a network. The
target directory ends up a copy of the source directory, but extra reverse
diffs are stored in a special subdirectory of that target directory, so you
can still recover files lost some time ago. The idea is to combine the best
features of a mirror and an incremental backup. rdiff-backup also preserves
subdirectories, hard links, dev files, permissions, uid/gid ownership (if it
is running as root), and modification times. Finally, rdiff-backup can operate
in a bandwidth efficient manner over a pipe, like rsync. Thus you can use
rdiff-backup and ssh to securely back a hard drive up to a remote location,
and only the differences will be transmitted.
WWW: http://rdiff-backup.stanford.edu/
Reminded by: kris and roberto
