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 04:23:51 -0800 
2006 -------
ericb->is

Thank you for your long answer, but I fear this is not what we expect. I'll try 
to describe better what we 
need, and if I'm wrong, please point what I miss.  Thanks in advance :-)

First, product version (and some other) infos are mandatory  _at_buildtime_ , 
because we create a 
bundle. scp2 won't help here, but I can be wrong.

About productversion.mk in sysui:  this is not a correct statement, and at 
least variables don't have to 
be in this module : one file containing these infos in solenv, is a more 
correct solution :

Imagine distributed build context : all modules can see solenv, not sysui 
content, whorse, other 
modules who need productversion : same issue.

Note :if several modules need the same info, this is a design problem, and 
again a global solution must 
be found.


ericb->mox

Thanks for your script, but this is my fault, I didn't present things 
completely :
I asked for a central point, in distributed build context.

Imagine other modules are not on the same level, for example sysui and desktop 
are not on the same 
machine : access sysui infos from desktop module becomes suddenly less 
easy/simple.

That's one of the reasons why I limited my suggestions to solenv and the solver.

The other one is unnecessary duplicated informations : maintainability is 
harder .. etc

Last but not least, if none disagrees, your script is ok for me.


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