I watched this thread for a while. I have subversion setups running with two of my customers and it's just really easy to setup, I really don't know what the painful thing is. The setups are always within-company, no need for svn+ssh, just via http is enough. Once Apache is configured correctly, it's just a matter of 'svnadmin create' to setup a new repos, and copy some standard config file into the repos. Easy to add to a script. I added some extra sweets to the script so it will setup a trac-environment as well resulting in a near perfect work environment. No need for reconfiguring Apache or whatsoever, just run the script with a single parameter (project name) and that's it. One note: my subversion repositories all live on Ubuntu servers.
I did not know about Mercurial / Git so that was interesting to read about. But as my setups need to be accessible for several programmers - some come and go - who appearantly all just happen to know about Subversion.
On 11/11/07, Allan Odgaard throw-away-2@macromates.com wrote:
On 10 Nov 2007, at 23:43, Thomas Aylott - subtleGradient wrote:
[...] For Subversion, since creating a repository is so painful, people tend to make a large repo that contains multiple subprojects. EG: Macromates bundle repo. For Mercurial, it would make the most sense to have a separate Mercurial project per project, or per bundle. Since it's not as easy to checkout only a subfolder of a project (afaik).
That should maybe be listed also as a downside of Mercurial/Git.
I.e. with Subversion a project is just a directory, everything you can do with a project (branch/switch, checkout, etc.) you can do with just a single directory (and be blissfully unaware of the rest of the project).
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate