Looks good, 

I was planning to start from scratch with building a RPM for 2.6 
that would work on at least RedHat 8.x AND 7.x.. Coincidentally,
this is something I planned to start on tomorrow! :-)

Instead, I'll take a few hours tomorrow to test your spec on 
RedHat 8.0, it would be *really* good if this could be the basis
of and future 2.6 / 2.7 packaging efforts...

> - anybody has opinions on the packaging layout.  Why is it advantageous
>   to have many packages rather than one?

Zope, Zope-zserver and Zope-PCGI packages seem like a good idea.
Most RPM dists seem to have at least a "-server" sub package if they
provide a daemon (eg postgresql). Init scripts, the "data" dir, etc 
all go in the "-server" subcomponent

[adam@blackbox adam]$ rpm -qa | grep postgresql
[adam@blackbox adam]$ rpm -ql postgresql-server

> - anybody has any opinions of where Zope files distributed via RPMs and
>   debs should really go, especially wrt to the Linux FHS.  I'm not sure
>   there is a right answer, but I don't know beans about this, so I 
>   figure I'll ask.  A file named 'Zope.spec.in' is attached to this 
>   email which is the input file to create a Zope RPM spec file during 
>   the make process, to give a better idea of how this works.

AFAIK on RedHat /opt or "mixed in" (/usr/bin etc) is fine, the argument
goes "if RPM tracks all the files for you, why use /usr/local or /opt?"
/opt is used too, the only problem being that it isn't often created
separate from the "/" partition, so there often isn't alot of space

One "trick" to note is for creating the inituser (from 2.5.1):

# Declare the Superuser of the Default Zope Project
  rm $RPM_BUILD_ROOT/usr/share/zope/inituser
  %{PYTHONAPP} $RPM_BUILD_ROOT/usr/bin/zpasswd -u admin -p 123
  chmod 0640 $RPM_BUILD_ROOT/var/zope/inituser

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to