Zope 3 installation layouts (Re: [Zope3-dev] ex zopeproducts directory in CookBook)

[Jim Fulton]

Paolo Invernizzi wrote:
> Jim Fulton wrote:
> 
>> - If a package is meant to be an example, it should be a top-level
>>   package in src. The package name should reflect the demon-ness,
>>   as in buddydemo.  It should be a top-level package because that's 
>> simplest
>>   and what many developers will do.  It should have a name with "demo" 
>> in it
>>   to make it's purpose clear and to get a flaw in Python's packaging 
>> system. :) 
> 
> 
> 
> *mumble* Well, in reality is the package used in recipes from Stephan's 
> book.
> We agreed in IRC to drop it in ZOPE3/src/book/messageboard "in the 
> recipe"...CVS donno!

I think that's fine. I encourage you to actually check it into the
CVS source tree so that it gets refactored with everything else.

> Basically, a newbie following the steps will create the package in his 
> local installation under ZOPE3/src/book/messageboard.

I think that's just fine.

In the story I provided, people will probably work on something like this
in the lib/python directory of an instance home.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org