[Zope-Coders] Re: Making Zope2 more LFH compatible

[Philipp von Weitershausen]

Christian Heimes wrote:

> Tres Seaver wrote:
> | I would say that the "SOFTWARE_HOME" bits should be written to a
> | version-qualified subdirectory:
> |
> |   /usr/lib/$ZOPE_VERSION
> 
> Great idea, but how:
> * Only major release number (zope2, zope3)
> * major + minor release (zope27, or zope-2.7)
> * or complete version number (zope-2.7.0)

For python, for example, Debian has different packages and different 
library paths for each minor release, e.g the package python2.2, 
contained Python 2.2.2 and when Python 2.2.3 was released, it contained 
2.2.3, thus /usr/lib/python2.2 was updated accordingly. I am running 
Python 2.1, 2.2 and 2.3 in parallel.

Something like this should also be possible with Zope then. I think it's 
  overkill to be able to run 2.6.1 and 2.6.2 in parallel. 2.6 and 2.7, 
for example, should be plenty...

> I'm for 2 or 3 with a softlink to /usr/lib/zope and/or /usr/lib/zope2

Yes, maybe. Also all "binaries" need to get a version suffix and 
symlinks (or even hardlinks) to their real name.

> |   /tmp/Zope-2.7/configure --enable-lsb
> 
> What is lsb?

Linux Standard Base, they standardize something you suggested: Linux 
filesystem hierarchy! :)

Philipp