[Grok-dev] grokproject putting Data.fs under parts/*
david.bain at alteroo.com
Mon Jan 12 13:02:25 EST 2009
I'm probably looking at this via Plone glasses, but.... I think var/* is
safer since buildout is wired only to "zap" stuff in parts/*. The fact that
there are circumstances when buildout deletes items in parts/* and no such
circumstances when it does this to items in var/* is a good reason to
consider placing Data.fs in var/*.
This is a well know pattern in the Plone buildout world (if that counts for
On Mon, Jan 12, 2009 at 12:39 PM, Wichert Akkerman <wichert at wiggy.net>wrote:
> Previously Martijn Faassen wrote:
> > Reinout van Rees wrote:
> > > Well, what every buildout guideline on plone.org seems to mention is:
> > >
> > > * Stuff in parts/* can and will be zapped into oblivion by buildout.
> > >
> > > * Stuff in var/* is safe.
> > > I cannot actually find it on buildout's pypi page, but I've always
> > > treated it as a rule of thumb. I could of course be something build
> > > several zope2-ish recipes.
> > I think that's the case. I've seen it before myself and I've been using
> > buildout in a Zope 3 context for many years now.
> > buildout doesn't zap parts into oblivion willy-nilly, it only zaps them
> > when there's an actual need (messing around with the [data] section will
> > do it, I suspect).
> Which includes:
> - moving your buildout to a different path on the filesystem and
> rerunning buildout
> - changing the configuration for the part
> both of these will make buildout delete data in parts/ and ask the
> recipe to recreate it.
> Wichert Akkerman <wichert at wiggy.net> It is simple to make things.
> http://www.wiggy.net/ It is hard to make things simple.
> Grok-dev mailing list
> Grok-dev at zope.org
SplashStart - Professional Websites. Starting Now.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev