是否有一个完整的文件系统版本控制的开源解决方案,其中版本库/库是远程的? [英] Is there an open source solution for full filesystem revision control where the revision db/repository is remote?

查看:222
本文介绍了是否有一个完整的文件系统版本控制的开源解决方案,其中版本库/库是远程的?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

问题:



有没有好的免费&打开解决方案在那里对整个文件系统进行修订控制?这包括这样一个问题:是否有任何典型的版本控制系统在这里工作(git,svn,bzr等)?

使用案例:

我们有文件系统映像,表示安装发生在我们的某些嵌入式系统,最后安装的文件可以有所作为。他们通常在开发,调试和维护过程中需要进行修改。这些变化需要与谁做的,为什么,什么时候一起存储。我们还需要能够区分变化,并恢复到特定版本。



修正文件系统听起来像是一个合理的妥协。但是我可以想到一些潜在的阻塞问题:


  • 提交身份验证,提交者&缺少用途追踪
  • 包含文件系统中的历史记录
  • 难以提交到共享库


解决方案

Rsnapshot BUP 都看起来很有前途,但是我没有详细信息。

<我会和BUP一起去,并会根据我的更多信息更新这个答案。


Question:

Is there a good free & open solution out there for revision control on an entire file system? This includes the question "would any of the typical revision control systems out there work for this (git, svn, bzr, etc.)?"

Use case:

We have filesystem images that represent installs that happen to some of our embedded systems where every last file installed can make a difference. They often require modification in the course of development, debugging, and maintenance. Those changes need to be stored along with who made them, why, and when. We also need to be able to diff the changes, and restore to particular versions.

Revisioning filesystems would sound like a reasonable compromise. However I can think of a few potential blocking problems:

  • commit authentication, and committer & purpose tracking missing
  • includes the history in the file system
  • hard to commit to shared repository

解决方案

Rsnapshot and Bup both look promising, but I don't have details.

I'm going with Bup, and will update this answer as I have more info.

这篇关于是否有一个完整的文件系统版本控制的开源解决方案,其中版本库/库是远程的?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆