the new cookutils feature that does install a standard package if relative dev package is specified in bdeps drives me crazy with Qt4-dev in cooking cookutils.
take e.g. libdbusmenu-qt receipt, which you fixed in tank:
as far as Qt4 does not exist locally (the file is named qt4) cookutils downloads a web package Qt4
Installing dep (web/cache): Qt4
reading the logs after builds fails i see that it install all of qt4 dependencies
Build dependencies to remove: 62 Removing: Qt4-dev QtDesigner alsa-lib cairo cdparanoia-III cmake dbus dbus-dev freetds gst-plugins-base gstreamer jpeg libQt3Support libQtClucene libQtCore libQtDBus libQtDesigner libQtGui libQtHelp libQtNetwork libQtOpenGL libQtPlugins libQtScript libQtScriptTools libQtSql libQtSvg libQtTest libQtWebkit libQtXml libdrm libegl-mesa libgio libglu-mesa libidn libjpeg libmysqlclient libogg liboil libpng libpostgresqlclient libtheora libtheora-enc libunixODBC libvorbis linux-agp linux-drm mesa pango pciids pixman qmake qt4-phonon qtconfig tiff udev usbids util-linux-blkid wget xcb-util xorg-libXv xorg-libXxf86vm xorg-libpciaccess
but as far as 4.8.4 is not in repo i assume that it install 4.7.3 dependencies, because the only way to get
libdbusmenu-qt builded is to modify the receipt in this way:
BUILD_DEPENDS="cmake qmake Qt4-dev libQtCore libQtDBus libQtGui dbus-dev wget"
so it install my local 4.8.4 packages and build it succesfully.
maybe we should move qt4 to Qt4?
or maybe cooker should check for local packages of meta's dependencies?
meanwhile i push my updated BUILD_DEPENDS to wok, it would get broken when 5.0 comes out.
PS it would get broken only if the server version is different from the local built version, but you never know :-)
PPS i previously cleaned my chroot and tazpkg removed 4.8.4 files from chroot.