Summary: | [EBUILD] MySQL Connector/C++ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hanno Zysik (geki) <h.mth> |
Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | VERIFIED FIXED | ||
Severity: | enhancement | CC: | office, yang |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forge.mysql.com/wiki/Connector_C++ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-db/mysql-connector-c++-1.0.6_pre754
dev-db/mysql-connector-c++-1.0.6_pre768 01_OOo_r271359.diff 02_no_README_LICENSE.mysql.diff 05_disable_tests.diff 06_disable_examples_build.diff dev-db/mysql-connector-c++-1.1.0_pre786 dev-db/mysql-connector-c++-1.1.0_pre786 dev-db/mysql-connector-c++-1.1.0_pre786 07_attribute_visibility_default_for_exceptions.diff dev-db/mysql-connector-c++-1.1.0_pre791 mysql-connector-c++-1.1.0_pre791.ebuild dev-db/mysql-connector-c++-1.1.0_pre814 |
Description
Hanno Zysik (geki)
2009-08-27 12:51:20 UTC
Created attachment 202393 [details]
dev-db/mysql-connector-c++-1.0.6_pre754
... from debian archive.
There will be a bump to revision 768 with test code and icu dependency removed. Just waiting for the tarball on debian archive. Created attachment 202580 [details]
dev-db/mysql-connector-c++-1.0.6_pre768
Since one cannot add optional cmake flags I have to patch the examples build.
Instead of 06_disable_examples_build.diff I would prefer to add '-DMYSQLCPPCONN_BUILD_EXAMPLES:BOOL=0' to the cmake command.
Created attachment 202582 [details, diff]
01_OOo_r271359.diff
Created attachment 202584 [details, diff]
02_no_README_LICENSE.mysql.diff
Created attachment 202586 [details, diff]
05_disable_tests.diff
Created attachment 202587 [details, diff]
06_disable_examples_build.diff
Created attachment 207072 [details]
dev-db/mysql-connector-c++-1.1.0_pre786
dev-db/mysql-connector-c++-1.1.0_pre786
- add openssl dependency
- add debug and gcov USEflag
- upstream cleaned up :)
I wonder about gcov USEflag.
And this piece of '$(use USEflag && echo 1 || echo 0)'.
use_enable and use_with fail. :)
Any better idea?
Created attachment 207074 [details]
dev-db/mysql-connector-c++-1.1.0_pre786
added use_cmake helper function.
Created attachment 210731 [details]
dev-db/mysql-connector-c++-1.1.0_pre786
- add RESTRICT for debug build
- some minor cosmetics
Created attachment 212445 [details, diff] 07_attribute_visibility_default_for_exceptions.diff See: http://bugs.debian.org/559219 Created attachment 212446 [details]
dev-db/mysql-connector-c++-1.1.0_pre791
dev-db/mysql-connector-c++-1.1.0_pre791 bump
Created attachment 224229 [details]
mysql-connector-c++-1.1.0_pre791.ebuild
addition:
- useflag [static-libs]
Created attachment 225089 [details]
dev-db/mysql-connector-c++-1.1.0_pre814
bump; cosmetics;
InCVS now. I had to clean up the libdir stuff more. Also used the patches straight from Debian, instead of having a duplicate copy. Are you interested in being a proxy maintainer for this package? Sure, why not. I test it with openoffice anyway. One question I have, though. How does portage handle a debug build? My experience is that, although one enables the useflag [debug], portage strips the debug symbols from the resulting binaries and libraries. That should not be, should it?! Hard to debug then... Therefore I use 'RESTRICT="debug? ( strip )"' to have the debug symbols in the binaries and libraries. USE=debug does not mean debug symbols. It means additional debugging code. # FEATURES=splitdebug CFLAGS='... -g ...' emerge CAT/PN will give you the debug data split off from the binaries, per the ELF debuglink spec. Alternatively, if you the monolith binaries with debug: FEATURES='-splitdebug nostrip -strip' ... Hanno Meyer-Thurow @16 FEATURES="nostrip splitdebug" maybe "installsources" http://www.gentoo.org/proj/en/qa/backtraces.xml man make.conf @Robin & @Francesco Thanks, I added that to /etc/portage/bashrc successfully. marked as verified. Finally got to test this package from portage. I wonder if you want to apply debians patch 04_libmysqlclient_SONAME.dpatch. That hardwires mysql-5.1 afais. So the ebuild may depend on '=virtual/mysql-5.1' instead. Or do mysql 5.4 and 6.0 have libmysqlclient_r.so.16, too? Another thing I wonder about is the useflag [static] versus [static-libs]. Looking at my world set it seems that programs use [static] and libraries, which dev-db/mysql-connector-c++ is, use [static-libs]. Whoever introduced the latter one ... (In reply to comment #20) > Finally got to test this package from portage. > > I wonder if you want to apply debians patch 04_libmysqlclient_SONAME.dpatch. > That hardwires mysql-5.1 afais. So the ebuild may depend on > '=virtual/mysql-5.1' instead. Or do mysql 5.4 and 6.0 have > libmysqlclient_r.so.16, too? 5.4, 5.5 and 6.0 do have the same SONAME version. static-libs was added for people that wanted some package to build dynamic binaries but static libs at the same time. |