History of CVS Migration
This is the notes about the bitweaver.org projects migration from CVS which makes extensive use of virtual modules (aka aliases ) in CVS to a distributed version control system (VCS) such as Mercurial or Git.
{| border=3
|+A Simple Table
|-
! Feature !! Git !! Mercurial
|-
! Ad-hoc Builds
| As of git 1.5.3, there is a concept known as [http://en.wikibooks.org/wiki/Git/Submodules_and_Superprojects|super modules]
|
|-
! Keywords
|
|
|-
! Cross Platform Support
|
|
|}
!Mercuial
!!Migration
#Migrate each module separately, and then combine
[http://stackoverflow.com/questions/12843/how-to-combine-two-projects-in-mercurial]
!Git
On CentOS, git needed to be upgraded to get super modules. CentOS 5.4+ broke things so the rpm would not build - had to [http://tonkersten.com/archives/2009/11/20/its_broken_again/index.html|docbook dtd definition] to get a Fedora rpm to build properly.
{| border=3
|+A Simple Table
|-
! Feature !! Git !! Mercurial
|-
! Ad-hoc Builds
| As of git 1.5.3, there is a concept known as [http://en.wikibooks.org/wiki/Git/Submodules_and_Superprojects|super modules]
|
|-
! Keywords
|
|
|-
! Cross Platform Support
|
|
|}
!Mercuial
!!Migration
#Migrate each module separately, and then combine
[http://stackoverflow.com/questions/12843/how-to-combine-two-projects-in-mercurial]
!Git
On CentOS, git needed to be upgraded to get super modules. CentOS 5.4+ broke things so the rpm would not build - had to [http://tonkersten.com/archives/2009/11/20/its_broken_again/index.html|docbook dtd definition] to get a Fedora rpm to build properly.