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

[Fred Drake]

On Thursday 22 April 2004 11:33 am, Jim Fulton wrote:
 >    We will still call this the software home.

This is a little different from Zope 2.  In Zope 2, the software home is the 
lib/python/ directory within the installation; the top-level directory of the 
installation itself is the "Zope home."  I like only naming the top-most 
directory better myself (and calling it the software home).

 >    Note that this will have a lib/python directory rather than a src
 > directory. This is to be consistent with distutil's notion of "home"
 > directories.

Which is a weird one at any rate.  But that's a distutils problem, not a Zope 
problem.

 > 3rd-party packages will be distutils-based packages build with a tool that
 > Fred Drake is working on. You will istall these like any other distutils
 > packages. In particular:
 >
 > - By default, they will install into your Python installation
 > (site-packages)
 >
 >    A problem with this option is that the zcml include file can't be
 > created. We'll need to give some though to this.
 >
 > - You will be able to supply a --home option to install the packages into
 > a software home or an instance home.

An idea I came up with on this is that the distributed package is a normal 
distutils package (and the tool I've been working on would be the easiest way 
to construct it), but we'd also install a script in the software home that 
allowed installing directly from a tarball into the software or instance 
homes.  (Distinguising between these targets could be done either by a 
command line option or by using a second version of the script installed in 
the instance.  I'm not sure which I like better.)


  -Fred

-- 
Fred L. Drake, Jr.  <fred at zope.com>
PythonLabs at Zope Corporation