Efforts/Package Restructuring/Versioning

Problem

OOo products and derivatives started to be composed of three layers with ?SB83?

• URE
• OOo Basis
• Brand

E.g.

• URE 1.4.1
• OOo Basis 3.0.2
• OOo Brand 3.1.3

Solution

The version ID of a particular OOo or derived product consequently has to be created out of the version numbers of these layers, e.g.

"OOo Brand 3.1.3-OOo Basis 3.0.2-URE 1.4.1"

Optimizations

As any brand layer directly depends on the major.micro version of the basis layer, the basis layer of any particular OOo installation may only vary with the micro version of the basis layer. That means, providing the micro number of the basis layer only, e.g. in the version string, is sufficient. Similar with the URE and OOo basis, the URE for a particular basis may only vary in its minor or micro numbers, thus providing the minor and micro numbers again is sufficient.

Some parts of this rather longish version number may be left out, leading to

"OOo 3.1-0-4.1"

where

• 3.1 stands for the brand layer version, while
• 0 is the the micro of the Basis layer, while
• 4.1 is the minor.micro of the URE.

Minor or micros numbers may be defaulted to zero, and left out in the version string if the actual value matches the default (zero). E.g.

• URE 1.4.0
• OOo Basis 3.1.0
• OOo Brand 3.0.0

Leading to

"OOo 3-1-4"