To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51494
------- Additional comments from [EMAIL PROTECTED] Tue Jul 5 03:50:32 -0700 2005 ------- kr: It is quite a problem to manage OOo, but shouldn't we have a central place in the build process where the version gets "brandmarked" (somewhere)? UNO is yet another thing which should also get its own version number. Customized builds like those of Debian, Novell Ximian etc. would just give it their own version number. Would it really be that hard to implement -v (--version)? Easiest would be to simply have a text file coming along with OOo containing the version number. Anyway, if such an enhancement would be made - and I think it would be a very useful one - it would be nice to be able to get the implementation exposed as an API object, so that API developers can get the version number as well (without needing to run ./soffice -v in the shell). --------------------------------------------------------------------- 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]
