Note that there are some explanatory texts on larger screens.

plurals
  1. POGit or no Git - Large Binary File Versioning, but no merge needed
    text
    copied!<p>There are many prior conversations here on StackOverflow about versioning and SCM for binary files in a code base. But I haven't found any information about this particular project and use case I'm researching:</p> <p>I have a single parent binary file - very large at multiple gigs in size. From that file, I have hundreds of "children" who are the same size, but each child is slightly unique compared to the parent with very small differences.</p> <p>I'll never need to merge the children into the parent - so I need some serious advice and insight into how to save just the differences between 1 parent and n children:</p> <ol> <li>Save just the binary differences for each child. </li> <li>When that child is needed (for download, to implement, etc), re-compile it using the parent file + differences.</li> <li>NO MERGE needed - I'm just interested in saving differences to reduce file size for each child.</li> </ol> <p>I've worked a lot with GIT and I've seen some great messages here on StackOverflow about Git's amazing ability to process binary files for versioning, like <a href="https://stackoverflow.com/questions/4697216/is-git-good-with-binary">this one</a> here.</p> <p>But my needs are more simple - I want an awesome C or C++ backbone for saving binary file differences, and re-compiling the original files using those differences PLUS a parent file. That's it. Is there any fast solution like GIT but without the extra features?</p> <p>Many thanks - I'm trying to avoid re-inventing the wheel here.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload