Bernard,
Bernard Marcelly wrote:
> Issue 51494 is another aspect of the same problem. I
think you are
> trying to give too much information. It is possible to
get the identity
> of an official release with information like this:
>
> Product name = "OpenOffice.org"
> Product version = "2.0.2"
>
> The places to store these information already exist in
> /share/registry/data/org/openoffice/Setup.xcu
> The problem is that the version is filled as 2.0 for
any 2.0.x version
> whereas it is already filled, for example, with 1.1.4
for a 1.1.4 version.
Independent of what is already available in the Setup.xcu,
the problem
is, that there is not "reliable" global version
number. Different
parties are building OOo on different platforms, with
different feature
sets, different patch levels and different versioning
schemes.
Features may be installed as extensions etc.
>
> Maybe it could be possible to add the Build number, but
already with
> this information it is possible:
> - with a simple program reading the Setup.xcu, to find
out which PC's in
> a network must be updated,
Do not rely on the Setup.xcu, instead use what is provided
in/with the
installable packages. Use standard tooling as apt for
updating your systems.
> - dynamically (in a macro), to know if a given Basic or
API feature is
> usable on the running OpenOffice
Just query for the wanted interface, if it is available,
call on it,
otherwise report an error or workaround it.
> - provide a version identity as a command-line switch,
as requested in
> issue 51494.
As discussed in this issue, this is not reasonable.
>
> StarOffice may have specific problems with version
identity, I can't say.
There is actually no difference in respect to this for all
OOo based
products, including OOo itself.
>
> Bernard
Kay
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe api.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org
|