Oliver Braun wrote:
Hi Stephan,

Stephan Bergmann wrote:
The planned new (OOo 3.0) structures are as follows:

On Unix (Linux, Solaris):
- The URE product still by default will install to /opt/openoffice.org/ure (but only the /opt prefix is relocatable).
- The OOo product by default will install its three layers into
-- /opt/openoffice.org/ure
-- /opt/openoffice.org/basis3.0
-- /opt/openoffice.org3.0
 (where only the /opt prefix is relocatable).
- The StarOffice product, for example, by default will install its three layers into
-- /opt/openoffice.org/ure
-- /opt/openoffice.org/basis3.0
-- /opt/staroffice9
 (where only the /opt prefix is relocatable).

Is there a good reason to keep the minor (3.0) in the path names and thus to continue to lose (super-)user deployed dictionaries and UNO extensions when upgrading from e.g. 3.0 to 3.1 ?

- The versioning of the basis directory (3 vs. 3.0 vs. 3.0.0) is constrained by the compatibility characteristics of the interface between basis and brand layer: If we can keep that interface compatible among minors, we can label the basis directory just "3"; if we can only keep that interface compatible among micors, we need to label it "3.0"; if, however, we would not even manage that, we would need to label it "3.0.0". As it stands now, the interface will be rather thin, the brand layer only containing startup code for the executables (and the meat of the executables residing in the basis layer, with few simple entry points), some .ini/rc files, bitmaps, icons, configuration entries, extensions (which should only be programmed against the URE, anyway), etc. But---compatibility is a hard problem, so I am not sure we will manage to stay compatible between minors.

- For dictionaries, see the parallel sub-thread by Petr and Caolan.

- Shared extensions for now will always go into the brand layer, anyway. (Rationale: there are brands that bring with them brand-specific extensions.) Note that this could be changed in the future, by having three extension layers instead of the current two.

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to