Last week I added two extra options to the infrae.subversion buildout recipe. Update 2008-10-31: included in the current 1.4 release . First the small one, then the biggie:
BUILDOUT/parts/productcheckouts
you can get BUILDOUT/our_products
.as_eggs = true
option to your infrae.subversion part and the checked out directories will get installed as development eggs. Woohoo!We like to keep the configuration mostly in buildout, so one of the last things left was the BUILDOUT/src
directory with its svn:externals. In the new situation, we use infrae.subversion for that:
[buildout] ... [ourpackages] recipe = infrae.subversion urls = https://svn......my.product/trunk my.product https://svn......my.theme/trunk my.theme location = src as_eggs = true [instance] ... eggs = ${buildout:eggs} ${plone:eggs} ${ourpackages:eggs}
You can use it to advantage in a production checkout, too. It'll be virtually the same, apart from using a tag checkout instead of a trunk checkout. An alternative to setting up your own password-protected egg store and allowing username/password downloads from buildout.
My name is Reinout van Rees and I program in Python, I live in the Netherlands, I cycle recumbent bikes and I have a model railway.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):