Timeline for Deploy C#/C++ binaries incrementally by patching the difference
Current License: CC BY-SA 4.0
33 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2022 at 4:02 | history | edited | gapsf | CC BY-SA 4.0 |
added 218 characters in body
|
| Sep 24, 2022 at 3:43 | history | edited | gapsf | CC BY-SA 4.0 |
added 129 characters in body
|
| Sep 20, 2022 at 10:20 | comment | added | gapsf | community.chocolatey.org/api/v2/package/rsync/6.2.5 its just a zip file. There are no official binary releases. There is download.samba.org/pub/rsync/binaries/GitHub-CI-builds which needs dlls from cgwin project. | |
| Sep 20, 2022 at 8:04 | comment | added | sɐunıɔןɐqɐp | @gapsf: No I've never heard of an Windows implementation, so I'll try it out. Btw, the rsync windows binaries cannot be download from that website, do you know any other reliable website for downloading it? | |
| Sep 19, 2022 at 12:52 | review | Suggested edits | |||
| Sep 24, 2022 at 3:42 | |||||
| Sep 18, 2022 at 22:13 | comment | added | nanofarad | @sɐunıɔןɐqɐp If "random stuff" (which is not actually random) is a big enough issue, you may want to consider a build system or other strategies that assure you of reproducible builds. Then, you can rsync to your heart's content, because if the actual input code/version were equivalent, then the output is as well. | |
| Sep 18, 2022 at 19:26 | history | edited | gapsf | CC BY-SA 4.0 |
added 44 characters in body
|
| Sep 18, 2022 at 19:10 | history | edited | gapsf | CC BY-SA 4.0 |
added 24 characters in body
|
| Sep 18, 2022 at 19:01 | history | edited | gapsf | CC BY-SA 4.0 |
added 124 characters in body
|
| Sep 18, 2022 at 18:48 | history | edited | gapsf | CC BY-SA 4.0 |
added 13 characters in body
|
| Sep 18, 2022 at 18:27 | history | edited | gapsf | CC BY-SA 4.0 |
added 4 characters in body
|
| Sep 18, 2022 at 18:21 | history | edited | gapsf | CC BY-SA 4.0 |
added 4 characters in body
|
| Sep 18, 2022 at 18:08 | history | edited | gapsf | CC BY-SA 4.0 |
added 16 characters in body
|
| Sep 18, 2022 at 17:51 | history | edited | gapsf | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Sep 18, 2022 at 17:45 | history | edited | gapsf | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Sep 18, 2022 at 17:38 | history | edited | gapsf | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Sep 18, 2022 at 17:33 | history | edited | gapsf | CC BY-SA 4.0 |
deleted 2 characters in body
|
| S Sep 18, 2022 at 16:30 | review | First answers | |||
| Sep 18, 2022 at 18:47 | |||||
| S Sep 18, 2022 at 16:30 | history | edited | gapsf | CC BY-SA 4.0 |
added 319 characters in body
|
| Sep 18, 2022 at 16:02 | comment | added | sɐunıɔןɐqɐp | I see that rsync copies the whole file. The assumption that we would deliver the whole package of binaries to the client is wrong, given that all hashes are different. The solution I'm looking for should deliver just what has changed. And by that I mean to compute the in-file difference, and send just this difference, for every file which has changed. | |
| Sep 18, 2022 at 15:56 | comment | added | sɐunıɔןɐqɐp | We don't detect by using hashes obviously because this would always classify all files as being different. The PE Header of all files will always contains different version information, timestamps, and signatures, emitted by the build. So we currently ignore these and deliver the binary only if the rest of the fields are different. But the PE Header is gigantic, and very difficult to understand, even using good parsers like PE.NET. Furthermore, some C++ compilers wriite random stuff in some parts of the binary (the parts not contaiining any useful program instruction). | |
| Sep 18, 2022 at 15:09 | history | edited | gapsf | CC BY-SA 4.0 |
deleted 21 characters in body
|
| Sep 18, 2022 at 14:59 | history | edited | gapsf | CC BY-SA 4.0 |
added 51 characters in body
|
| Sep 18, 2022 at 14:42 | history | edited | gapsf | CC BY-SA 4.0 |
added 13 characters in body
|
| Sep 18, 2022 at 14:32 | history | edited | gapsf | CC BY-SA 4.0 |
added 13 characters in body
|
| Sep 18, 2022 at 14:23 | history | edited | gapsf | CC BY-SA 4.0 |
added 202 characters in body
|
| Sep 18, 2022 at 14:09 | history | edited | gapsf | CC BY-SA 4.0 |
added 6 characters in body
|
| Sep 18, 2022 at 13:52 | history | edited | gapsf | CC BY-SA 4.0 |
added 12 characters in body
|
| Sep 18, 2022 at 13:42 | history | edited | gapsf | CC BY-SA 4.0 |
added 3 characters in body
|
| Sep 18, 2022 at 13:34 | history | edited | gapsf | CC BY-SA 4.0 |
added 3 characters in body
|
| Sep 18, 2022 at 13:26 | history | edited | gapsf | CC BY-SA 4.0 |
added 217 characters in body
|
| S Sep 18, 2022 at 13:19 | review | First answers | |||
| Sep 18, 2022 at 16:05 | |||||
| S Sep 18, 2022 at 13:19 | history | answered | gapsf | CC BY-SA 4.0 |