This manual is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
A copy of the GNU General Public License is available as
You can also obtain it by writing to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
In the following sections, will use these convention:
Will refer to the Zope application server as described
by
Will refer to any software that extends the
capabilities of Zope, like ZEO
or ZODB.
Will refer to any software that extends the range
of available objects for Zope, like
ParsedXML.
Will refer to the Debian package for Zope.
Will refer to the Debian package for a generic
foo Zope Package or Zope
Product.
Will refer to Zope Public License:
occasionally it may be followed by a version number
V (i.e. ZPL-V).
Will refer to Filesystem Hierarchy
Standard as documented in the
Since we may not ask for the inclusion of any
ZPL-V under
The package named
Every Debian source package that intends to provide either
a Zope Package or Zope Product named
foo, should build the
Debian packages for softwares simply related to Zope
may use different name convention (i.e.
Any
This is the home for Zope software. Any
Zope Package or Zope Product,
must be installed under an appropriate
subdirectory in order to work.
Import files (i.e. those files that usually have
Python extensin scripts must be installed under
this directory. Administrators may provide
symbolic links to desired files on a per-instance
base.
Debian package
See
There are many ways we can handle this:
We may simply include
We may build a
We may build a
Debian package
This would surely decrease the disk space used by the
installation of several Debian packages of Zope
Components.
I would replace this with an example file
as soon as possible.
As you should know, Zope need to be restarted to let each new
component to be used, but
For reference, read the reports on Bug
See
See
Zope should be restarted in the
configuration phase of the package installation.
Zope should not be restarted in the
configuration phase. The
Zope should not be restarted in any case:
the system administrator will handle it.
Zope package must comply to the following rules once installed:
Python is an interpreted language and either
source or byte-compiled file are architecture
independent, so they should be placed under
Zope support the concurrent running of
independent instances. Each instance uses a set of
files that may be atered multiple times during its
life time, so INSTANCE_HOME path should be
relative to
CLIENT_HOME must be directory relative to
INSTANCE_HOME. Suggested path is
Any log file should be placed under
Any pid file should be placed under