Difference between revisions of "Version Control System"
From Freeside
(→Requirements) |
|||
| Line 25: | Line 25: | ||
* Web interface not completely unlike viewvc.cgi | * Web interface not completely unlike viewvc.cgi | ||
* Good support for moving/renaming files and whole directories (i.e. preserving history) | * Good support for moving/renaming files and whole directories (i.e. preserving history) | ||
| + | * Useful versions (incl. viewvc.cgi-alike) utility in Debian stable or backports (bzr: no) | ||
* What else? | * What else? | ||
Revision as of 17:30, 25 March 2010
Contents
Synopsis
We need to move off of CVS eventually.
Systems
The big three
- Git - all the cool kids are using it these days (C)
- Mercurial/Hg (python)
- Bazaar - Canoical/Ubuntu/Launchpad (python)
The dark horses
- monotone (C++)
- Darcs (haskell)
Not considering
- Subversion, if we're going to migrate, it might as well be to something better enough to bother
- Codeville, its dead jim
- Vesta, commercial abandonware, not distributed
- Aegis - a strange beast. Probably not for us.
Requirements
- Import from CVS, preserving history (not just tips of our three branches)
- Web interface not completely unlike viewvc.cgi
- Good support for moving/renaming files and whole directories (i.e. preserving history)
- Useful versions (incl. viewvc.cgi-alike) utility in Debian stable or backports (bzr: no)
- What else?
