To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110427 Issue #|110427 Summary|native0 integrated a (different from DEV300/cws mysqlc |onnector) mysqlc into OOO320? Component|tools Version|current Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P1 Subcomponent|www Assigned to|dv Reported by|rene
------- Additional comments from [email protected] Fri Mar 26 22:30:30 +0000 2010 ------- In a OOO320_m14 clone: $ ls my* mysqlc: images prj source version.mk mysqlcppconn: cppconn_config.pmk makefile.mk mysql-connector-cpp.patch download mysql_config.pmk prj oh? cws mysqlconnector was only integrated for DEV300. Was it intended that it went over to OOO320 via native0? (Who "fixed" it for rebranding and probably thus just merged the cws). If I look at e.g. mysqlc/version.mk: $ hg log version.mk Änderung: 263405:b562f62892bf Nutzer: obo <[email protected]> Datum: Tue Mar 09 12:48:44 2010 +0100 Zusammenfassung: #i10000# commit repaired changeset Änderung: 263399:28f77bc32e70 Nutzer: Dirk Voelzke <[email protected]> Datum: Thu Mar 04 16:00:23 2010 +0100 Zusammenfassung: native0ext:#161688# rebranding extensions ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Even more, those two copies (what went into OOO320 and what went into DEV300 via cws mysqlcppconn) differ; see attached patch. Was that intended? If yes, close this and nevermind, but as noone was told.. And if the changes done in OOO320 will get lost in DEV300 that's bad, too 1.0.1 final vs. 1.0.1 alpha.... And the version in OOO320 introduced again a build bug with internal mysqlcppconn (yes, it's a bug to -lmysqlcppconn in mysqlcppconn's build). Can this be cleaned up? please ASAP? --------------------------------------------------------------------- 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]
