To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99899
------- Additional comments from i...@openoffice.org Thu Mar 5 12:59:46 +0000 2009 ------- I really do not see any problem to have a file in version a.b.c.d in a package with version x.y.z. There is absolutely no correlation, even if it is the only file in the package. And there cannot even be a correlation, if packages and files have different version schemas, like oxt files and RPMs. And there is no need to omit the extension version. You only have to know, that extension in version 0.5.0.2 is part of OOo 3.1.0, in which all RPM packages have the version 3.1.0-<buildid>. This is absolutely simple and can be generated automatically. And believe me: Nobody realizes that he has to update the "packageversion" for this one package in the svn module setup_native, if the version of the oxt file was changed. This will not fit together in a very short time. I created cws native234 to fix this issue. --------------------------------------------------------------------- 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: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
