To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=72835
------- Additional comments from [EMAIL PROTECTED] Fri Dec 22 05:47:39 -0800
2006 -------
is -> ericb: The basic idea in the build process is, that all cvs modules, that
are built before instsetoo_native, do not need any information about
productname, productversion, productextension, default destination directory and
so on, and so on. And nearly all modules are built before instsetoo_native,
which creates the installation sets. Therefore everything built before
instsetoo_native can be used for any product with any version. Only
instsetoo_native knows, which product in which version in which language and
with which package format shall be created (except sysui, what is of course a
big error, that was introduced because of time pressure).
If there are files, that have to include the packagename or the packageversion,
this info has to be written into this files during packaging process in
instsetoo_native, not earlier. If this does not work for your files now, we have
to introduce a new process for this in the packaging process. During build time
of your cvs module, you have to use a placeholder, that is replaced in packaging
process.
Therefore I explained scp2, where are flags for files available, that are
evaluated during packaging time. For example the binary "soffice.exe" is
modified during packaging process, because it has to contain the productname.
setup.xcu is modified, because it has to know productname, productversion and
much more information.
mox script is of course a fix, because it uses the info from openoffice.lst,
but this is exactly what was not intended in our build process. Please introduce
a placeholder in your cvs module ( ${PRODUCTVERSION} ), that is replaced in
packaging process (for binary files we will probably have to expand the existing
process).
---------------------------------------------------------------------
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]
