Putting buildouts in svn

Wichert Akkerman wichert at wiggy.net
Wed Sep 12 21:54:39 UTC 2007


Previously Florian Schulze wrote:
> On Mon, 10 Sep 2007 21:42:46 +0200, Derek Richardson  
> <derek.richardson at gatech.edu> wrote:
> 
> >The Vice project is a top-level folder in the collective. Inside, there  
> >is the usual trunk/, branches/, and tags/. Inside trunk/ are several  
> >different packages targeted at Zope and Plone. I would like to add two  
> >buildouts, one for Zope 2 + Plone and another for Zope 3. Is there a  
> >standard or recommended way to add multiple buildouts to a project  
> >repository? I was thinking:
> >
> >Vice
> >   +- trunk
> >        +- buildouts
> >             +- plone3.0
> >             +- zope3.4
> >        +- collective.baseid
> >        +- collective.uuid
> >        +- plone.syndication.outbound
> >        +- plone.app.syndication.outbound
> >   +- branches
> >   +- tags
> >
> >I looked through a few projects in the collective to find a model, but  
> >didn't see one.
> >
> >P.S. Martin, this would be great info to have in your buildout tutorial.
> >
> >Thanks,
> >
> >Derek
> 
> Hi!
> 
> I normally put them on the same level as trunk branches etc.
> 
> Vice
>   +- branches
>   +- buildouts
>   +- trunk
>   +- tags

For larger projects that use multiple products and/or packages I tend
to put the buildouts at the same level as the products. In other words:

	Vice
	+- buildout
	|  +- devel
	|  +- production
	+- collective.something
	|  +- trunk
	|  +- branches
	|  +- tags
	+- collective.otherthing
	   +- trunk
	   +- branches
	   +- tags

Wichert.

-- 
Wichert Akkerman <wichert at wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.




More information about the Product-Developers mailing list