Determining the version number of installed OOo

This isn't strictly API, but I figure it's a good place to
ask.

I am using a program that installs my own application and
OOo.  The 
problem is I need OOo 2.0 and have to be able to check any
existing 
instance of OOo on the target computer and see what version
it is.  I 
know usually you can tell by the directory name, but I'm
working with 
some people that have gotten picky and done things like
specify the 
directories for programs they install so they can sort them
easily or 
so they don't have version numbers in the program
directories.

What I need to be able to do is to either read in a file to
my install 
program or run a program within the OOo directory tree and
scan it for 
a version number.  This works great in Linux. 
"soffice -help" gives a 
help message with the full version number.  The problem is
on Windows.  
Instead of sending output to the console, it pops open a
window, and my 
program can't read any output.

Is there a way to tell OOo, when you use "-help"
on Windows, to NOT open 
a window, just print the help message?  And, if there
isn't, is there 
any file in the install that I can count on to give the FULL
version 
number (as in 2.0.2 instead of 2.0 -- which may be an issue
later)?  I 
can either read output from running a program OR read a file
directly 
to determine that.

The one last thought is that the README files say 2.0.  Can
I count on 
the version numbers in README to always be compatible?  In
other words, 
if there is some serious bug or needed change after 2.0.2
that creates 
API compatibility or general behavior changes, will the
versions in the 
README files (or in any file) be changed?  For example, if a
serious 
bug is found that breaks compatibility, would the version be
changed to 
2.1?  As long as versions are the same in README files, can
I count on 
the binaries and API to be compatible as well?

Thanks for any help and/or insight!

Hal

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Bonjour Hal Vaughan

I have recently filed an issue on this problem
<http://www.openoffice.org/issues/show_bug.cgi?id=64345
>

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.

    Bernard

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

On Sunday 23 April 2006 06:34, 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
>
>
> 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.
>
>     Bernard

I noticed someone says this is intentional.  Are they of the
thought 
that as long as the version number specified stays the same,
everything 
is supposed to be compatible?

Hal

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

On Sunday 23 April 2006 05:54, Hal Vaughan wrote:
...
> The one last thought is that the README files say 2.0. 
Can I count
> on the version numbers in README to always be
compatible?  In other
> words, if there is some serious bug or needed change
after 2.0.2 that
> creates API compatibility or general behavior changes,
will the
> versions in the README files (or in any file) be
changed?  For
> example, if a serious bug is found that breaks
compatibility, would
> the version be changed to 2.1?  As long as versions are
the same in
> README files, can I count on the binaries and API to be
compatible as
> well?

Since writing this, before going to sleep, I had one of
those "drifting 
off to sleep" ideas and, luckily, remembered it when I
woke up.

Is there a list anywhere of the released version numbers and
the 
corresponding build numbers?  It's hard to find on the
site.  I found 
program/versionrc has the build number in it.  It'd be
easier to match 
the version number, but the build number would be workable.

Thanks!

Hal

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Am Sonntag, den 23.04.2006, 11:52 -0400 schrieb Hal Vaughan:
> On Sunday 23 April 2006 06:34, 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
>
> >
> > 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.
> >
> >     Bernard
> 
> I noticed someone says this is intentional.  Are they
of the thought 
> that as long as the version number specified stays the
same, everything 
> is supposed to be compatible?

Has someone had a look at the Windows equivalent of Unix'
"~/.sversionrc"?

I think it's in the registry or user file space ... (no
installation of
2.x on *nix available here, for 1.x it has all nubers).

Does that have the complete 2.x.x version number?

HTH,
Marc


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org