divvun / bidiff Goto Github PK

Hello,

Thank you for creating this work. It's proving to be quite handy for making and applying patches!

While experimenting, I noticed that the version of bidiff listed on crates.io is set to 1.0.0.

Meanwhile, this repo's Cargo.toml shows a version of 0.1.0.

What's more, there is a slight mismatch in the dependencies, as well: rayon, log, and proptest (dev dep) have slightly higher versions.

Would it be possible to merge the outstanding changes from the crates.io artifact into this repository's master branch?

Hi,

First I'd like to thank you for building this amazing piece of software. Really.

Currently the best ratio can be achieved by using --method zstd (ZStandard), but while it's a good option for good compression at a fast(er) speed, LZMA is still king when it comes to high(er) ratios.

I know that the demo app itself is just basically that: a demo tool. But it's great, and it makes it easier to integrate with this library in any programming language (via launching processes, instead of needing some sort of FFI with Rust).

Looks like comde already supports it, so it might just be a matter of integrating with its latest version.

Thank you so much.

Cheers.

Would you consider adding benchmarks on a compiled Linux kernel bzImage file? For instance, v5.3 "make defconfig" versus v5.4 "make defconfig"?

While I can test this locally easily enough, that wouldn't give results that can be compared with the other test cases in your benchmark table.

I am evaluating bidiff to be used to generate patches for an embedded system.
I found that it is a way faster than any implementation of bsdiff that I've tried so far.
It would be great to use both tools bidiff for generating the patch and bspatch for applying it.
Is there a way to generate a patch that is compatible with bspatch?
If not, is it a planned feature?