openbravo-isv team mailing list archive

[Gorka Gil <gorka.gil@xxxxxxxxxxxxx>]

Hi Brian,

We have just published 3.0RC3 and we are designing the Ubuntu package
for the Openbravo 3.0 series.

The requirements:
- A user of Lucid/Maverick should be able to install Openbravo 2.50 or 3.0.

Note: it's not needed that the user has the 2.50 and 3.0 installed at
the same time.

The proposal:
- Have two different packages: one for 2.50 and one for 3.0.

The wanted behavior:
- If a user installs 3.0 and the user already has 2.50: It will do a
remove of 2.50 (but WITHOUT purge).
- If a user installs 2.50 and the user already has 3.0: It will do a
remove of 3.0 (but WITHOUT purge).
- Since the remove doesn't delete the sources and the database, the
user can come back to the other version without lost his data.

Details of the packages:
- Each package will have different directories:
(/opt/OpenbravoERP-2.50 and /opt/OpenbravoERP-3.0)
- Since both package have a different base directory, each package
will have its own database cluster and tomcat instance.
- Both packages will use the same system user: "openbravo". And the
variables like CATALINA_BASE, ANT_OPTS... and so on will be related to
the user, and will be overwritten in the package installation.
- The 3.0 package should be related to the 2.50 package in a way that
it avoids installing both at the same time.

What do you think about the proposal of having two packages?

How, and what type of relation is needed to be specified so that these
two packages cannot be installed at the same time?
How about using the "Conflicts" statement in the debian/control file?

Thanks,
Gorka