To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110427
------- Additional comments from [email protected] Mon Mar 29 07:59:41 +0000 2010 ------- > fs->rene: you should compare the right things before weeping. The DEV300- > version which you used for comparison was never intended to be copied to > OOO320. If we would have done so, you would probably have cried, too, since > this is indeed an alpha version, which differs from the release extension. No, I wouldn't. Actually I right now have a extension still based on mysqlnative and had mysqlconnector backported now. > Instead, the version from CWS mysqlnative (at a point in SVN where this CWS > did not yet see unsuccessful cross-code-line rebase attempts) which was > released as 1.0.0 was copied over to the OOO320 code line, with minor > adjustments. Aha. So it was intended. Good that people actually get told. > mysqlc-ppconn.diff contains the differences between the released 1.0.0 > extension version, and the version in OOO320.m14. As you can see, this is > indeed basically rebranding (plus a change to the extension's OXT file name, > whose cause I do not know, but which is certainly uncritical). - EXTENSION_ZIPNAME:=$(EXTENSIONNAME)-$(EXTENSION_VERSION_BASE)-$(MYSQLC_STATUS:s/ /-/:l)-$(RTL_OS:l)-$(RTL_ARCH:l) + EXTENSION_ZIPNAME:=$(EXTENSIONNAM I'd not call this "rebranding" but "changing the extension identifier" Besides that, what you added to OOO320 DOES miss the buildfixes I did in cws mysqlnative. Should I really need patches to apply myself again because you cannot get them over properly? > Resolving issue as INVALID. If you wish, I now now that the merge was intended (of course no one told anyone) but that the extension identifier changes is BAD. And the lost buildfixes too. --------------------------------------------------------------------- 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]
