summaryrefslogtreecommitdiff
path: root/sysutils/rdiff-backup/patches
AgeCommit message (Collapse)AuthorFilesLines
2003-08-14Update rdiff-backup to 0.12.3 (Also fixes PR pkg/22095)abs2-24/+8
- Over 1500 lines of changelog since 0.10.2 - Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a compressed text file in the rdiff-backup-data directory - No longer seems compelled to send symlinks every time
2003-03-22Update to 0.10.2, from PR 20268 by David S.wiz1-4/+4
Minor bugfixes.
2002-10-15Initial import of rdiff-backup-0.10.1 into the NetBSD Packages Collection.agc2-0/+37
Provided in PR 18577 by David.S at idiom dot com, some modifications by me to use buildlink2 files, and to specify the correct version of python required. 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.