11-25-2022, 11:16 PM
(This post was last modified: 11-25-2022, 11:19 PM by doppler.
Edit Reason: after thought.
)
(11-25-2022, 08:36 PM)a740g Wrote:(11-25-2022, 01:36 PM)doppler Wrote: Hello, Following on from the subject line....
I while back, in some other forum likely. I saw and used a program (dumb me never saved it). That would allow revision changes to take the original program and files. And update it to a new release. This would serve two purposes. The program changes need only be downloaded (much smaller), and the updated program is verified/changed as needed. By doing it this way, I don't have to migrate or integrate my stuff to a new release.
The real take away is. The change file is much smaller, faster download and less space of hard drive (like that a real problem still. Sorry I am old school ie: $100 for 5MB mfm drive).
Thanks.
Binary diff (daemonology.net)
mendsley/bsdiff: bsdiff and bspatch are libraries for building and applying patches to binary files. (github.com)
Edit:
There is also xdelta
jmacd/xdelta: open-source binary diff, delta/differential compression tools, VCDIFF/RFC 3284 delta compression (github.com)
Ding, Ding, Ding we have a winner. I sorta knew the program might start with an X re:xdelta. But my memory came up with NADA!
I am also advocating the minor releases provide an xdelta mod file, from the most current release to next. So when 3.4.1 rolls into 3.4.2, xdelta should be an option. The benefit from doing it that way. A previous forum posting more that likely was an overlay of 32 <> 64 bit code. Resulting in failure to compile. Because xdelta does not modify other than code or the specified files. A copy/move is not needed for your source files. It's an inline change.
Just occurred to me: There is no way to specify best answer in the new forum. That was the best answer.
PS. I will look at the other delta code changers, I like options.