ERP5Dependencies:

First of all, ERP5 needs python and Zope, but this is not at all enough. ERP5 also needs many zope Products, developped by many different developpers. We will see in this document the list of all products that we need in order to run ERP5. We will also describe how we can manage to have a simple way for the installation of ERP5.

DependenciesList:

This is two lists needed in order to use ERP5, the first one is the list of Zope Products, and the second is the list of extensions for python.

Zope Products :

      CMFCore
      DCWorkFlow
      Base18
      CMFDefault
      CMFTopic
      Localizer
      CMFWiki
      BTreeFolder2
      CMFPhoto
      Photo
      CMFMailIn
      Formulator
      ZSQLCatalog
      ZMySQLDA
      CMFReportTool

Python extension :

      Sax2 (xml extension for python)
      mysql driver for python
      reportlab for python

Also, ERP5 is itself made of 5 products :

      ERP5
      ERP5Catalog
      ERP5Form
      ERP5SyncML
      ERP5Type

Building RPMS :

A good solution to manage dependencies is to build packages, and make them dependent of some other packages. Most of the time, there's not already a rpm package that we can use. That's why we had to build a lot of rpm packages. You can find thoses rpm in the document called MandrakeERP5.

Since we want to share the work on packages, we added to the source code of ERP5 the spec files of all rpm on wich we are working. They are located inside the ERP5/spec folder. There is also in this folder a file called Makefile, it will be used to build in a very simple way new rpm packages from the source code. This Makefile take the source code from the CVS then build a archive file (.tar.bz2), then thanks to the spec file, the makefile can build a rpm. It is also used by the Nexedi company for the synchronisation with the rpm server, so that it is possible to update ERP5 with urpmi.

If you want the makefile to work, you should create a cvs directory inside your folder, the checkout the source tree of ERP5, ZSQLCatalog, Base18 and may be also Coramy.

Then you can go to the directory where there's the makefile, then you can simply run :

      make

This will create a rpm for ERP5, ERP5Catalog, ERP5Type, ERP5Compatibility, ERP5SyncML, Coramy, ZSQLCatalog and Base18 with the content of the last source code from the cvs. Nexedi developpers can enter make nex-all, this is the same thing plus the synchronisation with the rpm server (we can't provide access to the rpm server to everyone !).

The makefile also calls a script called build-rpm, this script is really powerfull since it allows to generate the more boring part of the spec file. It take cares that we never forget any files from the cvs. So instead of updating by hand the makefile after every update of the code, this is done automatically.