atom feed17 messages in org.freebsd.freebsd-archAdding bsdiff to the base system
FromSent OnAttachments
Colin PercivalMar 30, 2005 3:47 pm 
Ceri DaviesMar 31, 2005 2:16 am 
Alexey DokuchaevMar 31, 2005 2:24 am 
Colin PercivalMar 31, 2005 2:33 am 
Colin PercivalMar 31, 2005 2:47 am 
Robert WatsonMar 31, 2005 9:06 pm 
Mario HoerichApr 1, 2005 5:43 am 
Dan NelsonApr 1, 2005 7:27 am 
Garance A DrosihnApr 1, 2005 12:16 pm 
Alex BurkeApr 1, 2005 1:18 pm 
Colin PercivalApr 1, 2005 2:12 pm 
Max LaierApr 1, 2005 3:26 pm 
John BaldwinApr 2, 2005 12:15 pm 
Ceri DaviesApr 4, 2005 8:45 am 
Olaf WagnerApr 6, 2005 11:49 pm 
Colin PercivalApr 7, 2005 12:35 am 
John PolstraApr 8, 2005 8:11 am 
Subject:Adding bsdiff to the base system
From:Colin Percival (coli@wadham.ox.ac.uk)
Date:Mar 31, 2005 2:33:57 am
List:org.freebsd.freebsd-arch

Ceri Davies wrote:

On Wed, Mar 30, 2005 at 03:47:55PM -0800, Colin Percival wrote:

I'd like to add bsdiff/bspatch into the base system.

While it's probably easy to guess from the names, can you explain what they are?

Oops. bsdiff constructs a "binary diff", and is designed to produce particularly small patches when the two files differ by a large number of substitutions relative to the number of insertions and deletions (this is significant since executable files tend to change in this manner, as a result of linking object files together). Compared to other "binary diff" tools, bsdiff often produces patches 3-5 times smaller; however, it has the disadvantage of being slower and rather more memory-intensive than other tools.

bspatch is the opposite of bsdiff -- it takes the "old" file, the binary diff file, and produces the "new" file.