openbravo-isv team mailing list archive

[Juan Pablo Aroztegi <juanpablo.aroztegi@xxxxxxxxxxxxx>]

Hi Brian,

I'll reply to this last part, Gorka will take care of the rest:

> I know you've explained it a number of times, but can you detail for me
> again why you're moving files around in the way you are?  I might be able to
> come up with a better solution.  It was a major sticking point with our
> archive admins last go around and I'd like to improve the situation with the
> -3 package if at all possible.

Sure! Here's the rationale behind this: starting from version 2.50 and
also in 3.0 Openbravo is a modular application, similar to Eclipse. It
has a module management console within the ERP itself that allows you to
install and update modules. This means that Openbravo's standard
procedure to update to apply updates is using this console inside the
ERP. And as of now it's the only way of updating the ERP. We don't have
a way of delegating the updates to a third party program (like apt), it
would create big conflicts and it would result on a broken application.

Every time you install module or update the ERP this console rebuilds
the required java files and updates the database. That is, after using
the module management console every Openbravo instance has a unique
directory tree, different from any other instance's. This means that an
external program like apt cannot touch those files.

And this is why we do the directory copying:

* /usr/share/openbravo-erp/ contains a clean copy of a fresh
  installation, which is updated by apt every new release.

* The first time you install the package this tree is copied into the
  path Openbravo uses: /opt/OpenbravoERP-3.0/openbravo-erp. And this is
  the directory we cannot touch externally.


Please let me know if there's something which is not clear.


Regards,

Juan Pablo