FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation

[Chris McDonough]

On Wed, 2003-06-18 at 23:13, Adrian van den Dries wrote:
> Distribution install - most common::
> 
>   ./configure.py --prefix=/usr \
>                  --skel=/usr/share/zope/skel \
>                  --doc=/usr/share/zope/doc
> 
>   mkzopeinstance.py /var/lib/zope/default
>   
>   ln -s /var/lib/zope/default/etc /etc/zope/default
>   
>   echo -e '[default]\n/var/lib/zope/default' >> /etc/zopectl.conf


I think you are suggesting that all Zope config files be put into
/etc/zope with a "master" zope config file at /etc/zopectl.conf.

If so, I think this might make a lot of sense for a managed-binary Zope
multi-instance controller, but this is more a function of Luca's
framework than the Zope source installer.  I consider "my job" done
after someone runs mkzopeinstance.

>   zopectl.py start default
> All the above is invoked by ``apt-get install zope``, and the package
> can use a /etc/init.d/zope to loop through all instances.

This looks like it's a function of Luca's 'zopectl'; not ZC's, but given
that it sounds reasonable to me.

> Multiple pythons, zopes, instances - most complex::
> 
>   cd Zope-2.7.1
>   python2.1 configure.py --prefix=/opt/zope271-python21

(FWIW, configure is a shell script.)

> 
>   # ...
> 
>   python2.1 configure.py clean
> 
>   python2.2 configure.py --prefix=/opt/zope271-python22
> 
>   # ...
> 
>   cd ../Zope-2.7.2
> 
>   python2.1 configure.py --prefix=/opt/zope272-python21
> 
>   # ...
> 
>   python2.2 configure.py clean
> 
>   python2.2 configure.py --prefix=/opt/zope272-python22
> 
> Then you permute these with:
> 
>   python2.1 /opt/zope271-python21/bin/mkzopeinstance.py \
>             /var/zope/zope271-python21-instance1
> 
>   python2.2 /opt/zope271-python22/bin/mkzopeinstance.py \
>             /var/zope/zope271-python22-instance1
> 
>   # etc.
> 
> And you have an installation with all permutations of multiple
> Pythons, multiple Zopes and multiple instances.

Are you implying that the stuff that currently goes into
software_home/lib/python would be installed to the site-package
directory of the Python that was used to invoke the installer?  If so,
the subsequent invocations above of:

   cd Zope-2.7.1
   python2.1 configure.py --prefix=/opt/zope271-python21
   make; make install

   cd ../Zope-2.7.2
   python2.1 configure.py --prefix=/opt/zope272-python21
   make; make install

... would cause the Zope 2.7.1 libraries to be stomped by the Zope 2.7.2
libraries.

> Does this alleviate your concerns? ;-)

If you mean that the libraries are installed into
/opt/zope27X-python21/lib/python, there's no problem and nothing about
the installer needs to be changed.

So, in any case, given that the ZC source tarball installer will not
attempt to manage multiple instances (we'll leave that to Luca) here are
the requirements I've gathered so far:

- Add a --doc flag to configure
- Add a --skel flag to configure (is this a common pattern?)

Possibly:

- Make it possible to install Zope libraries into the site-packages
directory of the Python that invokes Zope's setup.py instead of into
software_home/lib/python.

Am I missing anything?

- C



> 
> a.
> 
> -- 
>  Adrian van den Dries                           avdd@flow.com.au
>  Development team                               www.dev.flow.com.au
>  FLOW Communications Pty. Ltd.                  www.flow.com.au
> 
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists - 
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope )