dev-python/pycairo can use svg surface
What exactly do you suggest?
I suggest use-dep (x11-libs/cairo[svg?] or explicit x11-libs/cairo[svg])
I would recommend a dep of cairo[svg], and +svg in cairo itself.
Fixed.
With the conditional use flag dependency of '[svg=]' I get the message >emerge -pv pycairo emerge: there are no ebuilds built with USE flags to satisfy ">=x11-libs/cairo-1.8.8[-svg]". !!! One of the following packages is required to complete your request: - x11-libs/cairo-1.8.8 (Change USE: -svg) (dependency required by "dev-python/pycairo-1.8.8" [ebuild]) (dependency required by "pycairo" [argument]) I have svg enabled for cairo emerge -pv cairo [ebuild R ] x11-libs/cairo-1.8.8 USE="X glitz opengl svg -cleartype -debug -directfb -doc -xcb" 0 kB So pycairo in effect tells me to turn off svg for cairo because it is not enabled for pycairo - doesnt seem right. Perhaps [svg?] as suggested above?
(In reply to comment #5) Current dependency is correct. "svg" USE flag must be either enabled for both cairo and pycairo, or disabled for these packages.
Thanks. Would it better to have a message saying something along those lines, rather than just indicating the one option of - x11-libs/cairo-1.8.8 (Change USE: -svg) I guess that is more portage than individual ebuilds?
(In reply to comment #6) > (In reply to comment #5) > > Current dependency is correct. "svg" USE flag must be either enabled for both > cairo and pycairo, or disabled for these packages. This is not acceptable. It leads to huge deptree issues when pycairo[-svg] and something else _requiring_ svg surfaces (so they depend on cairo[svg]). cairo[svg=] dep in pycairo means that if pycairo is build with USE=-svg, and you have something else, say, something everyone will have like pango, which requires svg surfaces, your deptree is screwed.
Seems like pycairo just shouldn't have an svg flag. People who want svg behavior should set the flag on cairo, and then pycairo will automagically get it.
I suppose the problem is the automagic bit too. Can't it be made explicitly configurable in the build system? So you could have cairo[svg] and pycairo[-svg] fine (you could now too, just I guess pycairo will still have svg support then without fixing automagic stuff).
