[Zope-Coders] Making Zope2 more LFH compatible

[Christian Heimes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For now Zope2 isn't very LFH (linux filesystem hirachie) compatible. The
last few changes from Chris gave me the idea to write this proposal how
the the filesystem layout should be altered:

/usr/share/doc/zope - documentations

/usr/share/zope - shared files like skeletons under /usr/share/zope/skel

/usr/bin - zopemkinstance, zopemkzeo, zopectl ... (renamed utilities)

/usr/lib/zope - zope main files

/usr/lib/$PYTHON_VERSION/site-packages/Zope - softlink to or files from
$ZOPE_HOME/lib/python/Zope/

/var/lib/zope/$INSTANCE_NAME/ - per instance data like zodb, products,
imports ...

/var/log/zope/$INSTANCE_NAME/ - zope logs

/var/run/zope/$INSTANCE_NAME/Z2.pid - pid file

/var/lock/zope/$INSTANCE_NAME/Z2.lck - lock file

/etc/zope/$INSTANCE_NAME.conf - configuration files per instance

/etc/zope/__default__.conf - default configuration which could be
overwritten by /etc/zope/$INSTANCE_NAME.conf

The reason for having logs, lock and pid file in sepereate directories
is that zope could run under different user accounts.

See you at EuroPython
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQE+8ec+9aLWrfOU0PgRAln1AKCNl4lj8Il8Sjo6c8XCIpvr2v4/JQCdEKhd
VUewAZMXAxLOPMAYXSpZHz4=
=ShcR
-----END PGP SIGNATURE-----