Elfshaker: Version control system fine-tuned for binaries
11–20 of 115 posts
Re: Elfshaker: Version control system fine-tuned for binaries
#12I find the description a bit confusing, is there and example where we can see the usage?
Re: Elfshaker: Version control system fine-tuned for binaries
#13Re: Elfshaker: Version control system fine-tuned for binaries
#14I find the description a bit confusing, is there and example where we can see the usage?
Re: Elfshaker: Version control system fine-tuned for binaries
#15Re: Elfshaker: Version control system fine-tuned for binaries
#16I find the description a bit confusing, is there and example where we can see the usage?
Same here. There is a usage guide, which helped a tiny bit: https://github.com/elfshaker/elfshaker/blob/main/docs/users/... Honestly, I sort of looked at it for conventional backup strategy...as in, i wonder if it could work as a replacement for tar-zipping up a directory, etc. But, not sure if the use cases is appropriate.
Re: Elfshaker: Version control system fine-tuned for binaries
#17Does it make a sense to turn it into fuse fs, with transparent deduplication?
Re: Elfshaker: Version control system fine-tuned for binaries
#18This should be integrated with Cargo to reduce the size of the target directories which are becoming ridiculously large.
Re: Elfshaker: Version control system fine-tuned for binaries
#19Huh, interesting, could you maybe use this as an in-repo alternative to something like git-lfs?
Re: Elfshaker: Version control system fine-tuned for binaries
#20Does this work well with image files? (PNG, JPEG, etc)
* There are many files,
* Most of them don't change very often,
* When they do change, the deltas of the binaries are not huge.
So, if the image files aren't changing very much, then it might work well for you. If the images are changing, their binary deltas would be quite large, so you'd get a compression ratio somewhat equivalent to if you'd concatenated the two revisions of the file and compressed them using ZStandard.