slackbuilds/development/bsdiff
Heinz Wiesinger 63daf9f79a All: Support $PRINT_PACKAGE_NAME env var
Signed-off-by: Heinz Wiesinger <pprkut@slackbuilds.org>
2021-07-17 21:55:09 +02:00
..
README development/bsdiff: Fix README. 2020-10-17 09:38:55 +07:00
bsdiff.SlackBuild All: Support $PRINT_PACKAGE_NAME env var 2021-07-17 21:55:09 +02:00
bsdiff.info development/bsdiff: Fix download URL. 2020-11-14 17:16:47 +07:00
slack-desc development/bsdiff: New maintainer, tweaks. 2018-12-15 20:44:28 +07:00

README

bsdiff (binary diff/patch utility)

bsdiff and bspatch are tools for building and applying patches to
binary files. By using suffix sorting (specifically, Larsson and
Sadakane's qsufsort) and taking advantage of how executable files
change, bsdiff routinely produces binary patches 50-80% smaller than
those produced by Xdelta, and 15% smaller than those produced by
.RTPatch (a $2750/seat commercial patch tool).

These programs were originally named bdiff and bpatch, but
the large number of other programs using those names lead to
confusion; I'm not sure if the "bs" in refers to "binary software"
(because bsdiff produces exceptionally small patches for executable
files) or "bytewise subtraction" (which is the key to how well it
performs). Feel free to offer other suggestions.

bsdiff is quite memory-hungry. It requires max(17*n,9*n+m)+O(1) bytes
of memory, where n is the size of the old file and m is the size of
the new file. bspatch requires n+m+O(1) bytes.

bsdiff runs in O((n+m) log n) time; on a 200MHz Pentium Pro, building
a binary patch for a 4MB file takes about 90 seconds. bspatch runs in
O(n+m) time; on the same machine, applying that patch takes about two
seconds.

Providing that off_t is defined properly, bsdiff and bspatch support
files of up to 2^61-1 = 2Ei-1 bytes.