Or maybe it mozsvg should now be a global(or whatever it's called) USE flag, maybe renamed to svg?
i vote for just enabling it ;)
I think that until more than one ebuild start using that option, we can start considering whether it shoud be global not. For now, I vote making it optinal but local... Radek
There is one more ebuild than mozilla-firebird, that already uses it, and that ebuild is mozilla...
configure: error: SVG requires a modified version of libart. To pull and build this LGPL library, set MOZ_INTERNAL_LIBART_LGPL, and then rerun the checkout stage Right now it looks like enabling SVG in mozilla-firefox isn't cut and dried. It's been disabled in mozilla for quite a while now. My understanding is that firefox just merged the new SVG code bug it appears that we don't have the libart in portage that we need. Suggestions?
This definitely doesn't work in firefox-0.8 right now. I tried the same code snippet that works in mozilla... # Re-enabled per bug 24522 (28 Apr 2004 agriffis) if use mozsvg; then export MOZ_INTERNAL_LIBART_LGPL=1 myconf="${myconf} --enable-svg --enable-svg-renderer-libart" else myconf="${myconf} --disable-svg" fi It failed with the following error... gmake[2]: Entering directory `/var/tmp/portage/mozilla-firefox-0.8-r3/work/mozilla/other-licenses/libart_lgpl' gmake[2]: *** No rule to make target `export'. Stop. gmake[2]: Leaving directory `/var/tmp/portage/mozilla-firefox-0.8-r3/work/mozilla/other-licenses/libart_lgpl' gmake[1]: *** [tier_1] Error 2 gmake[1]: Leaving directory `/var/tmp/portage/mozilla-firefox-0.8-r3/work/mozilla' make: *** [default] Error 2 !!! ERROR: net-www/mozilla-firefox-0.8-r3 failed. !!! Function src_compile, Line 206, Exitcode 2 !!! (no error message) I'm not going to enable something that is clearly not in a working state upstream. Resolving WONTFIX for now. Feel free to reopen or file another bug if SVG is fixed in a future version of firefox