[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2007-01-26 Thread of
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Fri Jan 26 02:31:09 -0800 
2007 ---
OF: Looks good for me in OOo2.2 OOFm3

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2007-01-26 Thread of
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User of changed the following:

What|Old value |New value

  Status|VERIFIED  |CLOSED





--- Additional comments from [EMAIL PROTECTED] Fri Jan 26 02:31:35 -0800 
2007 ---
closed

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-12-15 Thread of
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User of changed the following:

What|Old value |New value

  Status|RESOLVED  |VERIFIED





--- Additional comments from [EMAIL PROTECTED] Fri Dec 15 02:47:39 -0800 
2006 ---
OF: Looks good for me in cws native72.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-12-14 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User is changed the following:

What|Old value |New value

 Assigned to|pb|of





--- Additional comments from [EMAIL PROTECTED] Thu Dec 14 07:03:36 -0800 
2006 ---
IS - OF: Looks good in cws native72. Please verify.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-12-05 Thread pb
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User pb changed the following:

What|Old value |New value

  Status|NEW   |RESOLVED

  Resolution|  |FIXED





--- Additional comments from [EMAIL PROTECTED] Tue Dec  5 00:54:47 -0800 
2006 ---
pb: fixed in cws native72.
Files changed:
/officecfg/registry/schema/org/openoffice/Setup.xcs 1.50.98.1
/officecfg/registry/data/org/openoffice/Setup.xcu 1.28.94.1
/svx/source/intro/iso.src 1.12.636.1
/svx/source/intro/ooo.src 1.17.14.1
/desktop/source/app/app.cxx 1.199.2.1
/unotools/inc/unotools/configmgr.hxx 1.20.50.1
/unotools/source/config/configmgr.cxx 1.44.12.1


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-11-17 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User is changed the following:

What|Old value |New value

 Assigned to|is|pb

  Status|STARTED   |NEW





--- Additional comments from [EMAIL PROTECTED] Fri Nov 17 06:37:49 -0800 
2006 ---
IS - PB: I have added the new variable ABOUTBOXPRODUCTVERSION into the product
definition files. Please add a new entry into setup.xcu with the following 
content

prop oor:name=ooSetupVersionAboutBox
value${ABOUTBOXPRODUCTVERSION}/value
/prop

and use ooSetupVersionAboutBox to display the version in the about box.


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-11-06 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Nov  6 02:13:35 -0800 
2006 ---
Well, that is all your opinion. We have an OpenOffice.org version 2.1 and
require a packageversion 2.1.0. That is very simple. In the past we had an
OpenOffice.org version 2.0 and package version from 2.0.1 to 2.0.4. The package
version was only used for installation, the 2.0 was used in the installed
product. 

I explained your question already several times. Please read my mails more 
carefully

* Why don't you use different values for PACKAGEVERSION in OOo and SO?
We have different version for OOo and SO. For OOo it is 2.1.0, for SO it is 
8.0.5.

* Why do you need another variable if the PACKAGEVERSION already shows the
requested information?
That is your opinion. The requested version inside OpenOffice.org is 2.1, not
2.1.0. Therefore we need a new variable in setup.xcu, which will be set to
2.1.0 for OOo. But for StarOffice, we do not want to set this variable to
8.0.5, but to 8 (the ProductVersion).  And there is only one way to give values
from variables from the installation into the product. And this is code like 
this:

prop oor:name=ooPackageVersion
value${PACKAGEVERSION}/value
/prop

Unfortunately this would lead to 8.0.5 for StarOffice in the AboutBox. And
that is not what we want to have. Therefore we need a new variable, that
contains the value of PACKAGEVERSION for OOo and for PRODUCTVERSION for SO.
Otherwise we would have to make this differentiation in the sourcecode or
introduce two versions of setup.xcu.



-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-11-06 Thread andreschnabel
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Nov  6 03:01:16 -0800 
2006 ---
 We have an OpenOffice.org version 2.1 and
 require a packageversion 2.1.0. That is very simple. In the past we had an
 OpenOffice.org version 2.0 and package version from 2.0.1 to 2.0.4. The 
 package
 version was only used for installation, the 2.0 was used in the installed
 product.

And this is a misbehaviour, what lead to several Issues (63680, 61849, 58850,
60581, 60710, 59131, 58571, 61548) Please note, that some of these issues even
request more detailed information.

I don't know, how user experience came to the conclusion, that we do not need
the exact packageversion in Help-About. This information is important for users
who try to request help or report bugs.

If you don't like this behaviour for SO, you need to change it in SO, not in 
OOo.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-11-06 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Nov  6 03:42:25 -0800 
2006 ---
Don't mix this up please. This are several issues. The difference between
ProductVersion (2.0) and PackageVersion (2.0.0 to 2.0.4) is not a problem that
is caused by SO. Until now, there was no way, to add the PackageVersion to the
installed office. We want to fix this with this task and that will solve all
your problems. We want to fix this in a way, that ProductVersion and
PackageVersion are both available to the installed Office. And we want to fix it
in a way, that the value of PackageVersion is shown in the AboutBox of OOo and
that the value of ProductVersion is shown in the AboutBox of SO. And therefore
we want to introduce a new variable, that contains for OOo the value of
PackageVersion and for SO the value of ProductVersion. That is all and that is
really not a big problem.


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-11-03 Thread cloph
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Fri Nov  3 13:57:37 -0800 
2006 ---
 PackageVersion is the version of the (unix) packages. Therefore we introduced 
 a three-digit version number a.b.c. For OpenOffice.org this is currently 
 2.1.0 

Yes. And having a packageversion that doesn't match the version of OOo that's
included in the package doesn't make sense at all.

 openoffice.org-core01-packageversion-minor.i586.rpm

Not minor, but release...

 This number is only used for packaging reasons. It is not used in the Office
 products (except the OOo about box ;-) ).

So why introduce another variable that duplicates this and has even less usage?

Your comment unfortunately doesn't answer my question.

* Why do you need another variable if the PACKAGEVERSION already shows the
requested information?
* Why don't you use different values for PACKAGEVERSION in OOo and SO?

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-31 Thread cloph
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Tue Oct 31 05:29:28 -0800 
2006 ---
More simple question reduced to the minumum:
Why don't you set PACKAGEVERSION in openoffice.lst to 2.1.0 and PACKAGEVERSION
in staroffice.lst to 8?


And again: I'm *not* talking about different nodes/properties in Setup.xcu

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-31 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Tue Oct 31 07:40:27 -0800 
2006 ---
PackageVersion is the version of the (unix) packages. Therefore we introduced a
three-digit version number a.b.c. For OpenOffice.org this is currently 2.1.0
and for StarOffice this is 8.0.5. This is for example used in the spec files,
from which the Linux RPMs are generated. Therefore the RPMs have names like:

openoffice.org-core01-2.1.0-5.i586.rpm

which comes from 

openoffice.org-core01-packageversion-minor.i586.rpm

This represents the RPM naming schema.

This number is only used for packaging reasons. It is not used in the Office
products (except the OOo about box ;-) ). The Offices use only the official
numbers 2.1 or 8.
 

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-30 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Oct 30 01:48:27 -0800 
2006 ---
Well, I know that the user experience team decided, that this product is an
OpenOffice.org 2.0, which now becomes an OpenOffice.org 2.1. This product is
not an OpenOffice.org 2.1.0. Therefore the global variable ProductVersion,
that is used in setup and in Office is set to 2.1. We cannot change it for the
Office to 2.1.0, that is only used for packaging reasons, but has nothing to
do with the Product version.  If you want more specific information in AboutBox,
there has to be a new variable, that contains for OOo the same value as package
version. For this I want to introduce ${ABOUTBOXPRODUCTVERSION}. By the way: For
StarOffice we want to show StarOffice 8 and not something like StarOffice
8.1.0 and we do not want to introduce two versions of setup.xcu ;-)

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-30 Thread cloph
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Oct 30 02:43:02 -0800 
2006 ---
please read more carefully.

I wasn't talking about PRODUCTVERSION, but about PACKAGEVERSION

And as I already wrote: This variable already exists.

 that contains for OOo the same value as package version

So why use a copy if you can use the original?

And I doubt that Sun uses openoffice.lst as source for the variables.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-30 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Oct 30 03:19:46 -0800 
2006 ---
I read very carefully. Please read my explanation more carefully. The important
file for assignment of values from openoffice.lst to Office products (OOo and
SO) is the setup.xcu, in which the values are set during packaging process.
There you find the following code snippet:

prop oor:name=ooName
value${PRODUCTNAME}/value
/prop
prop oor:name=ooSetupVersion
value${PRODUCTVERSION}/value
/prop

The complete code from OOo and SO uses ooSetupVersion from the configuration
as internal product number. And this has to be 2.0 or 2.1 or simply 8 for
StarOffice. It would be a big error, to exchange ${PRODUCTVERSION} with
${PACKAGEVERSION} , because we would change the Office internal ooSetupVersion
from 2.1 to 2.1.0 and from 8 to 8.1.0. This is a big error, because the
Office code expects the Product version (which is defined as OpenOffice.org
2.1), when asking for ooSetupVersion. The package code is not expected and
currently even not transferred to setup.xcu, because no one asked for this
number until yet. Therefore we need a new variable in setup.xcu, that contains
for OOo the PACKAGEVERSION and for SO the PRODUCTVERSION, because we do not want
to show the package version in the about box.

Of course Sun does not use the openoffice.lst, but until yet Sun used the same
setup.xcu. But this is not the main problem. Instead the main problem is, that
the snippet:

prop oor:name=ooSetupVersion
value${PACKAGEVERSION}/value  // !
/prop

is forbidden by user experience, because this product is an OpenOffice.org 2.1
and not an OpenOffice.org 2.1.0.


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-30 Thread cloph
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Oct 30 03:36:12 -0800 
2006 ---
Read my first comment again.

It is *not* about Setup.xcu (although I still think that wouldn't matter) - It
is about why it should be necessary to introduce another variable that just
duplicates PACKAGEVERSION

But still:
You write when one would exchange the value ooSetupVersion in setup.xcu
 This is a big error, because the Office code expects the Product version 
 (which is defined as OpenOffice.org 2.1), when asking for ooSetupVersion

Show me a piece of code that would break here. I used my patch for a long time,
with the SetupVersion being set to 2.0.x and didn't observe any problem.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-30 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859





--- Additional comments from [EMAIL PROTECTED] Mon Oct 30 04:10:51 -0800 
2006 ---
In setup.xcu we have to introduce a new snippet like 

prop oor:name=ooPackageVersion
value${PACKAGEVERSION}/value
/prop

because we want to have both: ooSetupVersion and ooPackageVersion.
Of course no code breaks, if you exchange 2.1 by 2.1.0. This is a problem of
user experience. If someone wants to get the Productversion (2.1) with his
code, you cannot give him 2.1.0, because this is only a technical number,
which should be invisible to the user.  

And if we introduce something like 

prop oor:name=ooPackageVersion
value${PACKAGEVERSION}/value
/prop

this breaks the code, that displays the version in the AboutBox. For SO there
only has to be written a 8 and not a 8.1.0. Therefore we would have to
duplicate the setup.xcu - One version for OOo and one version for SO. And
therefore I prefer to introduce a new variable, that is identical with
PACKAGEVERSION for OOo and identical with PRODUCTVERSION for SO. 
Not nice, but the smallest problem for me, who always adapts this numbers. 



-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-27 Thread is
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User is changed the following:

What|Old value |New value

  Status|NEW   |STARTED





--- Additional comments from [EMAIL PROTECTED] Fri Oct 27 02:45:40 -0700 
2006 ---
Currently the setup.xcu contains an entry:

prop oor:name=ooSetupVersion
value${PRODUCTVERSION}/value
/prop

PRODUCTVERSION is set in openoffice.lst to 2.1. We do not know all places, in
which ooSetupVersion is used, therefore we have to introduce a new setting in
setup.xcu and in openoffice.lst. This is then only used for the aboutbox dialog:

prop oor:name=ooSetupVersionAboutBox
value${ABOUTBOXPRODUCTVERSION}/value
/prop

where the propery ABOUTBOXPRODUCTVERSION can be set to 2.1.0, 2.1.1, ...



-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-27 Thread cloph
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859


User cloph changed the following:

What|Old value |New value

Keywords|  |oooqa





--- Additional comments from [EMAIL PROTECTED] Fri Oct 27 13:49:00 -0700 
2006 ---
Having a different element in  Setup.xcu is somewhat understandable, (although I
*really* doubt that the value is used anywhere else, and if it is, I doubt it
matters whether the value is major.minor or major.minor.micro)

But why do you need another value ${ABOUTBOXPRODUCTVERSION} instead of
PACKAGEVERSION that already is available in openoffice.lst?

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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



[installation-issues] [Issue 70859] New variable (full version ) in setup.xcu

2006-10-25 Thread pb
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=70859
 Issue #|70859
 Summary|New variable (full version) in setup.xcu
   Component|Installation
 Version|680m188
Platform|All
 URL|
  OS/Version|All
  Status|NEW
   Status whiteboard|
Keywords|
  Resolution|
  Issue type|ENHANCEMENT
Priority|P3
Subcomponent|code
 Assigned to|is
 Reported by|pb





--- Additional comments from [EMAIL PROTECTED] Wed Oct 25 08:10:14 -0700 
2006 ---
Please provide a new variable in setup.xcu. We need it to show the full version
number on the about dialog. For OOo it should be like 2.0.4 or 2.1 or 2.1.1 and
for SO only 8 or 9.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

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


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