[Zope-Packagers] DISCUSS: Making RPMs

[Paul Everitt]

Adam Manock wrote:
> Initial requirements for a Zope RPM need to be nailed down.
> 
> So far, IMHO:
> 
> Zope >= 2.5.0 requires python2.1 >= 2.1.2 enforced by RPM (reduce 
> zope at zope.org list traffic :-)


... and I'm changing the stinking subject line.  Whew!

As Matt noted, he's working on an official proposal that sketches out an 
overhaul of the installation process.  I think we can keep discussing 
RPM-specific matters until we hear back from him.  For now, I'll try to 
respond to these points.

> Minimum of Zope data area broken out of main directory heirachy to a 
> /var/zope INSTANCE_HOME.

I think Matt will give us an answer here...

> standard chkconfig stuff, zope user creation, etc.
> 
> Undecided:
> 
> PCGI?
> Put zope-PCGI in a separate spec / source package? An additional 
> (optional to build and install) package?

I think it is reasonable to hide pcgi.  We *certainly* don't need it on 
by default.

> Narrowing the scope to only support zope w/zserver in the main package 
> initially = earlier initial release.

Right.

I have long thought that we should migrate binary stuff into a separate 
package.  Alternatively, have a zope-base that contains the minimum 
necessary, including C extensions.  This makes applying updates 
smaller/easier.

In the future, we might use this base package to get Python packages 
from a CPAN-like service (e.g. Kapil's) and Zope packages from a similar 
service.

--Paul