To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68817


User rt changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'hjs,is,rt'
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Mon Aug 21 04:57:27 -0700 
2006 -------
Sorry, but I do not really like the idea of module config_office grabbing around
in foreign modules (allthough that would be less bad than some ordinary module
or makefile doing so druing the build). If you need office's major, minor, and
micro version number outside the packaging process, I could image two solutions:
1) Pull that information out of instsetoo_native/util/openoffice.lst, put it in
some config file at f.e.solenv/config. Use it from there even for packaging.
2) Do not use these numbers explicitly but some variable which gets resolved by
office application during runtime. OpenOffice.org knows its version from
program/bootstraprc or program/versionrc.

In any case please note that there is not just one value of PACKAGEVERSION per
build. It's one value per product. For OOo we currently have (see
openoffice.lst) OpenOffice, OpenOffice_wJRE, and OpenOffice_Dev (currently all
with the same PACKAGEVERSION, but do not take that as guaranteed), and URE and
OpenOffice_SDK. For Sun internal build you can imagine that we have additional
products such as StarOffice, getting built in an internal module similar to
instsetoo_native. (This could make solution (1) more difficult because there may
be cases where Sun does not want to put versioning information for internal
products on a public module.)
Could you please give us some hint what you need that information for? You just
wrote "It is useful". The best solution may well depend on the use case you have
in mind.


---------------------------------------------------------------------
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]

Reply via email to