On Thu, Jul 22, 2010 at 04:49:46PM -0800, rogerx@sdf.org wrote:
# USE="cairo -doc -gif -ipv6 -jpeg -png -ssl" emerge dillo -pv
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds built with USE flags to satisfy "x11-libs/fltk:2[-cairo,-png,-jpeg]". !!! One of the following packages is required to complete your request: - x11-libs/fltk-2.0_pre6970 (Change USE: -cairo) (dependency required by "www-client/dillo-2.2" [ebuild]) (dependency required by "dillo" [argument])
In short, think I need to probably file a bug report against the Dillo ebuild??
OK. I found the culprit within the dillo ebuild: RDEPEND="x11-libs/fltk:2[-cairo,jpeg=,png=] Apparently, the Gentoo Dillo Ebuilds are scripted to check for fltk2 compiled without cairo support (ie. -cairo). When fltk is compiled with cairo support, the above error will result requesting fltk be recompiled without cairo support. Did a search for the words "dillo cairo" and "fltk cairo" and I find zero bugs ever filed for them. Is there any reason why Gentoo developers would demand fltk be built without cairo support? Any big evil or huge bug possible? Licensing?? x11-libs/cairo-1.8.8-r1.ebuild LICENSE="|| ( LGPL-2.1 MPL-1.1 )" Well, anyways -- building fltk with cairo (and needlessly recompiling dillo afterwards) support causes Dillo to constantly flicker making the user interface unusable. And still, copy/pasting always causes the copy buffer to end-up within the Dillo url entry field. :-/ As such, it's likely cairo isn't the culprit here.