[Grok-dev] grokproject putting Data.fs under parts/*

Andreas Jung lists at zopyx.com
Mon Jan 12 10:28:47 EST 2009

Hash: SHA1

On 12.01.2009 16:23 Uhr, Reinout van Rees wrote:
> Martijn Faassen schreef:
>> Hi there,
>> Andreas Jung wrote:
>>> why does grojprojekt configure the Data.fs to live under parts/data?
>>> Moving parts like the Data.fs should in general live outside the scope
>>> and the control of zc.buildout?!
>> That's not the opinion of the people who wrote the buildout recipes 
>> we're using. :)
>> The idea is that buildout can generate the whole setup for you, and that 
>> includes the database. The benefit is this that buildout can also 
>> potentially setup things like ZEO and so on.
>> You seem to have a philosophical difference with the people that wrote 
>> zc.recipe.filestorage and zc.zope3recipes... We've been following that 
>> pattern with Grok from the start and I'm not sure what you think is 
>> wrong with it.
> 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 agree with that. Stuff under parts/* can be removed and recreated
under control of buildout. Means recipes should be safe to remove their
part at-will. A removed Data.fs can not be restored by a recipe. That's
why the Data.fs file should be kept outside 'parts'.

Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lists.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090112/e82f59b8/attachment.vcf 

More information about the Grok-dev mailing list