PUBLIC MARKS with tag svn

Take control of Subversion with a client application that was specifically designed for Mac users. Cornerstone integrates all of the features you need to interact with your repository and does so in an elegant and easy-to-use fashion.

In contrast with my earlier attempts at migrating to git, mercurial was actually a joy to setup on the server. WSGI, using our existing .htusers file from Trac, a small config script, done. This contrast to git which would require some funky SSH sandboxing and/or PAM setup - yes it can be done, but such hacks shouldn't be needed.

To all our surprise "hg clone" was extremely fast even compared to subversion and especially in comparison to git.

Until recently, Pinax had two choices for a given external dependency:

1. use svn:externals and point to the external dependency's svn repository
2. include the external dependency code in the Pinax codebase

However, there are problems with this approach:

1. it largely relies on external dependencies being in svn and this is increasingly not the case (although it was when Pinax started)
2. it makes it difficult for Pinax itself to move away from svn
3. there is no management of dependencies between external dependencies, nor between particular projects in Pinax and their individual dependencies

To solve these problems and more, Pinax is switching to a distutils-based approach. This means:

1. externals dependencies are encouraged to be released as distutil-compliant packages with a valid setup.py and put on PyPI
2. development versions of dependencies can be pulled in in a variety of different ways including from git, hg or bzr repositories

svn:externals are evil

the evil is SVN itself not handling changing of externals (i.e. to/from an external) in basic operations like updates and merges, which may cause a lot of manual work on your end, and break automated builds or similar.

wondering about massively usage of it.