Ideas on setting up a Horde Git repository
This project is to determine what the next generation of the Horde will use to store and organize source code.
Some initial work has been done with Git and SVN conversions of the current CVS repository.
Today checking out a Horde app within an existing Horde checkout works fine. This includes making single-commit changes across applications.
Naturally no matter what we choose Chora support will either be added or will improve. However if it is already supported by Chora all the better.
In alphabetical order...
Bazaar from Canonical (i.e. the ubuntu company)
#!/usr/bin/env sh cd /var/www/git/horde/ export CVSROOT=":pserver:cvsread@anoncvs.horde.org:/repository" FILES="agora ansel chora <SNIP> whups wicked" for FILE in $FILES do echo $FILE": " git-cvsimport -C$FILE $FILE done
I added a git submodule for every horde module inside the horde/horde
repository. Now you can do:
git clone git://git.koch.ro/git/horde/horde cd horde git submodule init foreach modules as MODULE // Only those you want to use git submodule update $MODULE // checks out the module
Now there are some more things[1] to think about when actually developing, but
that's one way it could be done.
[1] http://git.or.cz/gitwiki/GitSubmoduleTutorial
ls -C -w60 agora goops jonah nag swoosh ansel groupware juno nic trean chora hermes klutz occam turba CVSROOT horde kronolith passwd ulaform dimp hordedoc luxor pearweb update.sh forwards hordeweb merk presentations vacation framework imp midas sam vilma genie incubator mimp scry volos gitgc.sh ingo mnemo sesha whups gollem jeta mottle skeleton wicked /var/www/git/horde$ du -hs 928M
Another alternative:
SCM | Full (Server) Repository Size | Branch Checkout |
---|
CVS | 51MB | 7MB |
SVN | 31MB | 16MB |
git* | 18MB | 18MB |
Back to the Project List