The ebuilds for FVWM say that gdk-pixbuf is a dependency if USE="imlib" is activated. That is not true. FVWM builds and installs just fine when compiled without gdk-pixbuf. It would be nice to have that corrected, because the way it is forces You to install half of gnome when You just wanted a lean windowmanager. BTW, this would be a good moment to update to the recent stable version FVWM 2.4.19 - currently the only ebuild for the stable branch of FVWM in portage is 2.4.18. Greetings, Dirk
Created attachment 76782 [details] Ebuild for FVWM 2.4.19 without gdk-pixbuf It would be good if someone would have a look on this before using it publicly ... ;-) Btw, afaik gdk-pixbuf is the graphics library of gnome (so it says on the e17 homepage). So, if someone really wanted to use fvwm with gnome he should have gdk-pixbuf anyway, and then the configure-script should automagically detect and use it, shouldn't it?
Just checking, does this bug also apply to fvwm 2.5.*? media-libs/gdk-pixbuf is pending removal, and is package.masked, so it is a bit annoying to have a stable package (fvwm-2.5.18-r1) depend on a masked one, even if the dependency is optional.
It looks like you're right. I've removed the dependency in cvs. RESOLVED => FIXED.
*** Bug 155454 has been marked as a duplicate of this bug. ***
