Bonjour Kay
Message du 2006-04-26 13:13:
Bernard,
Bernard Marcelly wrote:
Bonjour Hal Vaughan
I have recently filed an issue on this problem
<http://www.openoffice.org/issues/show_bug.cgi?id=64345>
If I understand correctly, this is double to
http://www.openoffice.org/issues/show_bug.cgi?id=51494
IMHO it is a defect that it is now impossible to know the exact
version number, since there are new functionalities, corrections of
bugs, and new bugs at each minor version.
Please have a look at the above mentioned issue for details regarding
not being able to get an (exact) version number.
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.
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,
- dynamically (in a macro), to know if a given Basic or API feature is
usable on the running OpenOffice
- provide a version identity as a command-line switch, as requested in
issue 51494.
StarOffice may have specific problems with version identity, I can't say.
Bernard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
