To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=72835
User is changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WORKSFORME
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Dec 21 02:44:35 -0800
2006 -------
is -> ericb:
instsetoo_native/util/openoffice.lst is exactly what you are looking for. This
is the file, in which you can define products. Many properties can be set in
this file, like ProductName, ProductVersion, ...
This file is the central start point for the packager, when a special product
with a special language has to be created. Some variables like ProductName and
ProductVersion are also written into the configuration files, so that they are
also available to the installed Office product during runtime.
No other place is allowed than instsetoo_native/util/openoffice.lst .
Unfortunately we need currently the hack, that the version also needs to be set
in sysui. But this is caused by the problem, that packages are created in sysui.
The correct way would be, to define the packages in scp2 and let the packager
create them. But this was not introduced because of time pressure.
For the Mac OS files, we should introduce a mechanism, that the ProductVersion
is written into this files (if this is really required) during the packaging
process. Perhaps you can use the mechanism, that we use for example for the
setup.xcu, where the content
<prop oor:name="ooName">
<value>${PRODUCTNAME}</value>
</prop>
<prop oor:name="ooSetupVersion">
<value>${PRODUCTVERSION}</value>
</prop>
<prop oor:name="ooSetupExtension">
<value>${PRODUCTEXTENSION}</value>
</prop>
<prop oor:name="ooXMLFileFormatVersion">
<value>${FILEFORMATVERSION}</value>
</prop>
<prop oor:name="ooXMLFileFormatName">
<value>${FILEFORMATNAME}</value>
</prop>
<prop oor:name="ooOpenSourceContext">
<value>${OPENSOURCE}</value>
</prop>
is replaced during packaging process to
<prop oor:name="ooName">
<value>OpenOffice.org</value>
</prop>
<prop oor:name="ooSetupVersion">
<value>2.1</value>
</prop>
<prop oor:name="ooSetupExtension">
<value></value>
</prop>
<prop oor:name="ooXMLFileFormatVersion">
<value>1.0</value>
</prop>
<prop oor:name="ooXMLFileFormatName">
<value>OpenOffice.org</value>
</prop>
<prop oor:name="ooOpenSourceContext">
<value>1</value>
</prop>
In scp you have to set the flag SCPZIP_REPLACE
File gid_File_Oo_Setup_Xcu
TXT_FILE_BODY;
Styles = (PACKED, SCPZIP_REPLACE,PATCH);
Dir = gid_Dir_Share_Registry_Data_Org_Openoffice;
Name = "/registry/data/org/openoffice/Setup.xcu";
End
This is even implemented for binary files like the soffice.exe. If you want to
patch such a file, you have to set in scp2 the flag PATCH_SO_NAME, to include
the ProductName.
So in my opinion there is nothing to do, because this central place already
exists and different processes are available to use the packaging process to
include this properties into different files.
---------------------------------------------------------------------
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]
