Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

14
  • 4
    Why specifically do you need incremental patches? Merely to reduce the amount of data that must be transferred to client systems? Or are there other implications for the deployment process? Commented Sep 18, 2022 at 11:05
  • 6
    I can't even 100% rule out that that is a good idea, but more in a "not even wrong" way... Have you considered that this might be an XY Problem? Commented Sep 18, 2022 at 19:51
  • 16
    A sensible versioning strategy would not require you to change the version of any DLL that hasn't otherwise changed. Commented Sep 18, 2022 at 21:38
  • 1
    The header files are distributed in different directories, not just the project's directory. There is a big chain of includes binding header files together. So it is not easy to track what source files affect exactly a given binary. I cannot change this, since it is a huge software in production and that would be extremely expensive. We are not talking about Disneyland, where everything is build perfectly from the beginning with best software practices. It's an humongous system running since the 90s, and still works well for the client. Advices on source code changes won't help at all. Commented Sep 22, 2022 at 9:06
  • 2
    Chromium have "courgette" for this, which itself compares against bsdiff: chromium.org/developers/design-documents/… Commented Sep 23, 2022 at 16:16