>>> Compiling source in /var/tmp/portage/x11-misc/dunst-1.2.0/work/dunst-1.2.0 ... make -j1 Package gdk-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gdk-2.0.pc' to the PKG_CONFIG_PATH environment variable Package 'gdk-2.0', required by 'virtual:world', not found ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_libressl_20170818-200954 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: emerge -qpv x11-misc/dunst [ebuild N ] x11-misc/dunst-1.2.0 USE="-dunstify"
Created attachment 490486 [details] emerge-info.txt
Created attachment 490488 [details] emerge-history.txt
Created attachment 490490 [details] environment
Created attachment 490492 [details] etc.portage.tbz2
Created attachment 490494 [details] temp.tbz2
Created attachment 490496 [details] x11-misc:dunst-1.2.0:20170824-154533.log
Fixed without revision bump.
The fix also altered dunst-1.1.0 which does not need gtk+2.0. Dunst 1.1.0 is working on my system that has installed gdk-pixbuf and cairo but no gtk+. The problem with 1.2.0 seems to be a call to gdk_cairo_set_source_pixbuf which requires the gdk-pixbuf <---> cairo integration and this is part of gtk+ on Gentoo. This is unfortunate for those of us that relied on dunst as a lightweight notification daemon not depending on any toolkit. I have masked 1.2.0 on my system, but I'd recommend removing the changes in commit 36428e84 to the stable 1.1.0 package since they are not needed.
(In reply to Reimundo Heluani from comment #8) > The fix also altered dunst-1.1.0 which does not need gtk+2.0. > > Dunst 1.1.0 is working on my system that has installed gdk-pixbuf and cairo > but no gtk+. > > The problem with 1.2.0 seems to be a call to gdk_cairo_set_source_pixbuf > which requires the gdk-pixbuf <---> cairo integration and this is part of > gtk+ on Gentoo. This is unfortunate for those of us that relied on dunst as > a lightweight notification daemon not depending on any toolkit. I have > masked 1.2.0 on my system, but I'd recommend removing the changes in commit > 36428e84 to the stable 1.1.0 package since they are not needed. Oops. Fixed.
