有没有工具可以在Windows上管理git中的大型二进制文件？ [英] Are there tools for managing large binary files in git on Windows?
问题描述
我已经熟悉一般问题的答案，如何在git（或大量文件）中管理大型二进制文件。我已经看过 git-annex ， bup ，以及 git-media。没有声称Windows用户访问非常好。
有没有这样的程序在Windows上运行良好？
< hr>
要添加上下文，我试图版本控制我的系统部署位：操作系统映像，驱动程序，第三方安装程序，第一方安装程序（我们的应用程序）。我需要把所有东西放在一个连贯的包（标签）中。
不是我知道的，而且正如你所知道的，大的二进制文件不兼容：
- VCS（因为在区分它们或合并它们时没有意义） li>
- DVCS（其中一个分布式回购是为了克隆，这是一个笨重的回购，很快麻烦）
剩下的唯一解决方案（实际上与操作系统无关）仍然是一个外部工件存储库（例如 Nexus ，实例）来存储这些二进制文件。
安东尼马斯特雷恩补充说，他需要：
版本控制我的系统部署位：操作系统映像，驱动程序，第三方安装人员，第一方安装人员（我们的应用程序）。
我需要有前夕什么东西在一个连贯的捆绑（标签）。并且能够为我们的任何活动版本获取整个包
这将是混合：
- 开发要求（版本控制，意味着分支和比较版本）
- / strong>（获取所有正确的标签以便部署和运行）
任何未开发的东西（即任何构建的东西或已经存在）应该不在VCS中（除非是非常小的资源，例如图标，这些资源变化不大）。
您通常使用的版本是发布文件，其中包含部署脚本的所有额外信息（校验和，其他参考的路径......） 来操作，获取正确的工件。
I'm already familiar with answers to the general question, how to manage large binary files in git (or a large number of files). And I've looked at git-annex, bup, and git-media. None claim very good access for the Windows user.
Are there any such programs that run well on Windows?
To add context, I'm trying to version control my system deployment bits: OS images, drivers, 3rd party installers, 1st party installers (our applications). I need to have everything in a coherent bundle (tags). And be able to get the entire bundle for any of our active releases.
Not that I know of, and as you know, large binary files aren't compatible with:
- VCS (since there is no sense in diff'ing them or merging them)
- DVCS (where a distributed repo is meant to be cloned, which is quickly cumbersome with an obese repo)
The only remaining solution (OS agnostic actually) remains an external artifact repository (like a Nexus one for instance) to store those binaries.
The OP Anthony Mastrean adds that he needs to:
version control my system deployment bits: OS images, drivers, 3rd party installers, 1st party installers (our applications).
I need to have everything in a coherent bundle (tags). And be able to get the entire bundle for any of our active releases
That would be mixing:
- development requirements (versioning, meaning branching and comparing versions)
- with deployment requirements (getting all the right labels in order to deploy and run)
Anything which isn't developed (i.e anything built or already existing) should be out of a VCS (except for very small resources, like icons for instance, which don't change much).
What you usually version is a "release file" which contains all the extra information (checksums, path to other referentials, ...) for the deployment script to operate, fetching the right artifacts.
这篇关于有没有工具可以在Windows上管理git中的大型二进制文件？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
