Plone2 RPM Package Page

Introduction

The plone2 rpms are expected to run on any modern rpm based distribution. The ony requirement is that you got python 2.3.3 installed by rpm.

What these RPMs should do

Install a Zope to /etc/plone2, /usr/lib/plone2 and /var/lib/plone2 (Configuration, Software, Instances).
Create a Zope instance 'main' in /var/lib/plone2/main.
Include all Plone2 products as specified in the dist_plone script. (Details).
Setup a initial Database using setupSite.py in the "main" instance.
Copy over an old Plone1 database from /var/lib/plone/Data.fs if found.
Provide a start script at /etc/init.d/plone2 start|stop|restart|status.
Provide logrotate integration.
Provide mkploneinstance and mkplonezeoinstance scripts for instance/zeo creation.
Provide zplonepasswd script for setting passwords.
Create a sytem user 'plone' with group 'plone'.
Run with uid and gid 'plone'.
Only listen on 127.0.0.1:8080 per default (Username/Password plone/plone).

Requirements

A modern RPM based linux distribution (see below).
Python 2.3.3 installed via RPM.

Fedora Core 2

Fedora Core 2 support in Plone 2.0.3 RPMs.

Since the release of Plone 2.0.3 RPMs there is builtin support for Fedora Core 2. The Source RPM should compile smoothly on Tettnang. It requires Python-2.3.3 and Python-2.3.3-devel which are standard on FC2. As my local Fedora Core 2 installation still refuses to run inside VMWare i wasn't able to build binary RPMs there yet.

If you rebuilt the SRPM on Fedora Core 2 please tell us by adding a comment below. To get the Source RPM scroll down until you reach the Source RPM section.

Important Notice:
  I had not much time the last weeks and didn't rebuild the RPMs. Scroll down the comments to see how to get it work on Fedora Core 2.

Red Hat 9.0 / EL 3, and Fedora Core 1 builds

If you got Fedora Core 1 or Red Hat Linux 9.0 / EL 3 and want to install Plone2 as RPM then see this section.

Dependencies

Python2.3-2.3.3 (see this HOWTO for details on installing Python 2.3.3 on Red Hat 9 / EL 3 or Fedora Core 1).

Required Files, MD5 checksums and sizes

df1a2a4586cab2e2195eb89b61eef467 Plone2-2.0.3-2.rh.i386.rpm (8951738 bytes)

SuSE 9.0 builds

If you got SuSE linux and want to install Plone2 as RPM then see this section.

Dependencies

Python-2.3.3 (see this HOWTO for details on installing Python 2.3.3 on SuSE 9).

Required Files, MD5 checksums and sizes

41d3093e27553108ebfa253fd93df165 Plone2-2.0.3-2.suse.i586.rpm (9227431 bytes)

Mandrake

Mandrake Linux Plone2 RPMs are not yet done. I expect this to happen soon.

You may want to try the RedHat / Fedora Linux RPM which has a good chance to work on Mandrake as well. This is not tested nor supported though.

If you want to help in finishing Mandrake support please contact me at simon@longsleep.org.

Building from SRPM (Source RPM)

When no binary RPM is a available for your distribution, version or architecture you have the option to rebuild a RPM for your installation from the source RPM.

Building from source RPM requires a lot of developement libraries installed. In short a whole developement system including compiler, header files and libraries which are required. This process produces full featured binary RPMs exactly for your architecture, version and distribution. After compiling you should be able to install the resulted RPM without problems.

Required Files, MD5 checksums and sizes

b3553c54f1d1a314b7b2a6fea6d37868 Plone2-2.0.3-2.src.rpm (6542434 bytes)

Building the source RPM

As root do a

>>> rpmbuild --rebuild Plone2-*.src.rpm

After some time a RPM is written to a location usually somewhere in /usr/src/. Install this with the usual "rpm -Uvh" command.

Feedback wanted

Please add a comment into this section to tell others on what platform you rebuilt the source RPM successfully.