git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSoC - Some questions on the idea of

From
NKNeal Kreitzinger <nkreitzinger@gmail.com>
Date
Apr 11, 2012, 18:23 UTC
Message-ID
<4F85CC0A.1020602@gmail.com>
In-Reply-To
<20120411060357.GA15805@burratino>
On 4/11/2012 1:04 AM, Jonathan Nieder wrote:
>
> I would suggest tracking source code instead of binaries if
> possible, though.
>

Reasons why we want to track binaries: (1) Standard Targets: Our deployment is assembly line style because our target servers are under our control. (2) Copy vs. Recompile: We run certain "supported" linux distro versions on our target servers so we can just put our binaries on them instead of recompiling. (3) In-house-Source Compiled Binaries: For our particular proprietary (third-party) source language the binaries run on top of a runtime that runs on top of the O/S so that makes the need to recompile on a server a non-issue. We use xxd and compile listings to "diff" our compiled binaries to detect missing copybook and data dictionary dependencies (missed recompiles), unnecessary recompiles (you didn't really change what you thought you changed), and miscompiles. We do this compiled binary validation in git branches and then diff the branches to detect the discrepancies. (4) Proprietary-Third-Party Binaries (no source) Versioning: For our third party binaries we don't have the source. The are distributed as self-extracting-executables. Changes to third party binaries are relatively infrequent but frequent enough to cause confusion and therefore need to be tracked. (5) Graphics "Source" Versioning: Our graphics files are part of our software and changes need to be tracked. (6) O/S Versioning: Our linux distro is tracked in a bazaar repo so I'm thinking we should be able to track it in a git repo instead. The assembly line just deploys the payload to a new server instead of doing manual install. (7) Superproject tracking of "Super-release": The above subsystems are related in varying degrees (dependent). A superproject can associate all the versions that comprise a "super" release of the various subsystem version dependencies.

While some of the reasons above may be non-normative for some git-users, I think that a large portion (if not the majority) of git-users will find some subset of the above reasons normative for their use-cases (namely reasons 5 and 4) therefore making the necessity for binary tracking normative for git-users in general.

v/r, neal

Previous: Jonathan NiederNext: Jeff King
Message 21 of 43 in “GSoC - Some questions on the idea of "Better big-file support".”
  1. Bo ChenMar 28, 2012
  2. Nguyen Thai Ngoc DuyMar 28, 2012
  3. SergioMar 28, 2012
  4. Bo ChenMar 30, 2012
  5. Bo ChenMar 30, 2012
  6. Jeff KingMar 30, 2012
  7. Bo ChenMar 30, 2012
  8. Sergio CallegariMar 31, 2012
  9. Neal KreitzingerMar 31, 2012
  10. Jeff KingApr 2, 2012
  11. Sergio CallegariApr 3, 2012
  12. Neal KreitzingerApr 11, 2012
  13. Jonathan NiederApr 11, 2012
  14. Neal KreitzingerApr 11, 2012
  15. Jeff KingApr 11, 2012
  16. Neal KreitzingerApr 11, 2012
  17. Neal KreitzingerApr 11, 2012
  18. Jonathan NiederApr 11, 2012
  19. Junio C HamanoApr 11, 2012
  20. Jonathan NiederApr 11, 2012
  21. Neal KreitzingerApr 11, 2012
  22. Jeff KingApr 11, 2012
  23. Neal KreitzingerApr 12, 2012
  24. Jeff KingApr 12, 2012
  25. Neal KreitzingerApr 12, 2012
  26. Bo ChenApr 13, 2012
  27. Neal KreitzingerMar 31, 2012
  28. Jeff KingApr 2, 2012
  29. Junio C HamanoApr 2, 2012
  30. Jeff KingApr 3, 2012
  31. Neal KreitzingerMar 31, 2012
  32. Neal KreitzingerMar 31, 2012
  33. Bo ChenMar 31, 2012
  34. Nguyen Thai Ngoc DuyApr 1, 2012
  35. Bo ChenApr 1, 2012
  36. Nguyen Thai Ngoc DuyApr 2, 2012
  37. Bo ChenMar 30, 2012
  38. Jeff KingMar 30, 2012
  39. Jeff KingApr 15, 2012
  40. Neal KreitzingerApr 15, 2012
  41. Jeff KingApr 16, 2012
  42. Neal KreitzingerMay 10, 2012
  43. Jeff KingMay 10, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.