-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/07/12 07:41 AM, Ben de Groot wrote: > On 12 July 2012 17:52, Rich Freeman <ri...@gentoo.org> wrote: >> On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot >> <yng...@gentoo.org> wrote: >>> Actually, there is another workable solution, and that is to >>> set USE="-gstreamer -icu" for qt-webkit. >>> >>> Currently we enable gstreamer by default in the ebuild (as it >>> is used for HTML5 audio/video, which is expected functionality >>> in qt-webkit based web browsers etc.), but we are considering >>> if we should perhaps not enable this by default. >> >> As discussed on the bug, this will likely help some, but it >> doesn't help anybody who uses KDE or Gnome. > > As far as I know the gstreamer useflag is only enabled in the > gnome profile, not the kde one currently. >
How much Gnome stuff needs qt-webkit? I figured that gnome stuffs would be much more likely to require webkit-gtk , yes? So a KDE user, with USE="-gstreamer" , is most likely not going to run into this issue yes? And Gnome users that have webkit-gtk[gstreamer] packages don't run into this issue with chromium anyways, right? (i know there's always overlap as anyone can install anything, but i'm thinking of the general scope of impact here) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAk/+1m0ACgkQ2ugaI38ACPBgQwD8DuLYiLZv4LUAuW1VACqRW/av npl1U7DXm8jqPM4l0B4BALR4FY+yUD824X2+UwbB6hAjEZrYpLSIQz2zINbUiLYK =vYhV -----END PGP SIGNATURE-----
