The gui client has got the dependency "mysql" in the ebuild. But this is (obviously, it's a client) not needed. It doesn't make much sence, to install a client only on the machine, where the mysql-server resides. An injected mysql-ebuild doesn't solve this, because while building, some real mysql-files are asked for. Perhaps looking in the RPM will help, that one doesn't depend on mysql (Mandrake). Greets, qd Reproducible: Always Steps to Reproduce: 1."emerge mysqlcc" OR 2."emerge -i dev/db/mysql-4.0.18" AND 3."emerge mysqlcc" Actual Results: Variant "2./3.": ... ... checking for mysql.h... checking for /usr/include/mysql.h... no checking for /usr/include/mysql/mysql.h... no checking for /usr/local/include/mysql.h... no checking for /usr/local/include/mysql/mysql.h... no checking for /usr/local/mysql/include/mysql.h... no configure: error: Could not find mysql.h in ' /usr/include /usr/include/mysql /usr/local/include /usr/local/include/mysql /usr/local/mysql/include' !!! ERROR: dev-db/mysqlcc-0.9.3 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed Expected Results: installing ;-) Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6. 3-gentoo-QD) ================================================================= System uname: 2.6.3-gentoo-QD i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3. 2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache sandbox" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http: //ftp.uni-erlangen.de/pub/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow X alsa arts artswrappersuid avi berkdb crypt cups dga doc dvd encode gdbm gif gpm gtk gtk2 imlib ipv6 java jpeg kde linguas_de maildir mmx mpeg ncurses nls oggvorbis opengl pam pdflib perl png python qt quicktime readline spell sse ssl tetex tiff truetype unicode wmf x86 xml xml2 xmms xv zlib"
mysqlcc needs the headers AND libraries from mysql. the position of gentoo is that we are NOT splitting up packages like the rpm world (-devel,-lib,-devel,-doc,-client,-server,-wtf,...) at this point in time. (this is under consideration for the next major version of portage, but that is LONG way off). if upstream does it and maintains them as seperate packages, then we will use those, but not otherwise. as such, the mysql package will not be split up to provide just the libs and headers, and mysqlcc does depend on mysql.
If you look here: http://rpmseek.com/rpm/mysqlcc-0.9.4-1mdk.i586.html?hl=de&cs=mysqlcc:PN:0:0:0:0:1004935&ShowFileList=1 Then you can see, that it does not depend on mysql. Or did i read that wrong? There are no mysql-libraries mentioned. Installing a complete database everytime i only want to use it via client is a little, very little overhead, or am i wrong? Perhaps this rpm is patched to fit this needs? Can't that be done in Gentoo, too? Greets, qd
in the rpm you linked to, mysqlcc is compiled statically against mysql, so the libraries aren't needed (since they are already inside the binary). the bug remains as it was, we are NOT going to split up mysql or any other packages ourselves at this point in time. as a note on the build times of MySQL, compiling it without the server part takes only a tiny fraction off of the compile time of the whole thing (assuming you don't enable innodb).