Debian Zope Policy
Chapter 3 - zope-foo package

3.1 Paths

Any zope-foo package should use the following paths or file guidelines:

/usr/lib/zope

This is the home for Zope software. Any Zope Package or Zope Product, must be installed under an appropriate subdirectory in order to work.

/usr/lib/zope/import

Import files (i.e. those files that usually have .zexp extension) must installed under this directory. Administrators may provide symbolic links to desired files on a per-instance base.

/usr/lib/zope/Extensions

Python extensin scripts must be installed under this directory. Administrators may provide symbolic links to desired files on a per-instance base.

tests directory

Debian package zope-foo may not provide any tests directory [2] [3].

3.2 Notable files

/usr/share/doc/zope-foo/copyright

Debian package zope-foo may not include any ZPL-V; it may simply refer to the license provided by the zope package in the /usr/share/doc/zope/ZPL-V file [4]. The copyright file in source Debian package may look like the following [5]:

     This is the Debian package of Zope foo component.
     
     This package was put together by Debian Developer <account@debian.org>,
     from sources obtained from:
     
       protocol://site/path
     
     Author: Upstream Author(s) <mail@upstream.address>
     
     Copyright:
     
     This software is distributed under the term of the Zope Public License version V.
     Please, refer to /usr/share/doc/zope/ZPL-V

3.3 Configuration and pre-configuration

As you should know, Zope need to be restarted to let each new component to be used, but zope-foo should not ask any question to administrators about this issue [6]. During the Debian package pre-configuration/configuration phase, zope package will prompt the shared/zope/restart shared Debconf question [7]: while configuring, zope-foo should use the answer to shared/zope/restart to decide how to configure the package. Possible reply are [8]:

configuring

Zope should be restarted in the configuration phase of the package installation.

end

Zope should not be restarted in the configuration phase. The postinst maintainer script should instead touch the /var/run/zope/restart file: this will trigger a test in /etc/apt/apt.conf.d/90zope that will restart Zope at the end of the whole installation or upgrade process.

manually

Zope should not be restarted in any case: the system administrator will handle it.

Debian Zope Policy