[Product-Developers] buildout with developing eggs without using svn:external

[Dylan Jay]

Hi,

I have a setup with where I have multiple plone sites on a single zope 
instance. I control this with two buildout .cfg files, devel.cfg and 
production.cfg.
I keep this under svn and for each site I create a theme as an egg link 
that into the buildout in svn via svn:externals. This works great for 
production and testing as a single svn update brings in all the correct 
code for each of the themes.
However during development I have several checkouts of this arrangement, 
one for each site I'm developing. svn update is site1_devel dir brings 
in all the themes and other eggs I've developed which aren't needed 
during development. This is a bit of a pain as its extra space and time.

My question is, is there a better way of bring in eggs being developed? 
esp one I can use inside a buildout.cnf so I can make if different 
between production and development.

Infrae.subversion recipe might have been good put it only checks out in 
the parts dir rather than src dir.

Any ideas?

Dylan.