| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 12/07/12 07:41 AM, Ben de Groot wrote: |
| 5 |
> On 12 July 2012 17:52, Rich Freeman <rich0@g.o> wrote: |
| 6 |
>> On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot |
| 7 |
>> <yngwin@g.o> wrote: |
| 8 |
>>> Actually, there is another workable solution, and that is to |
| 9 |
>>> set USE="-gstreamer -icu" for qt-webkit. |
| 10 |
>>> |
| 11 |
>>> Currently we enable gstreamer by default in the ebuild (as it |
| 12 |
>>> is used for HTML5 audio/video, which is expected functionality |
| 13 |
>>> in qt-webkit based web browsers etc.), but we are considering |
| 14 |
>>> if we should perhaps not enable this by default. |
| 15 |
>> |
| 16 |
>> As discussed on the bug, this will likely help some, but it |
| 17 |
>> doesn't help anybody who uses KDE or Gnome. |
| 18 |
> |
| 19 |
> As far as I know the gstreamer useflag is only enabled in the |
| 20 |
> gnome profile, not the kde one currently. |
| 21 |
> |
| 22 |
|
| 23 |
How much Gnome stuff needs qt-webkit? I figured that gnome stuffs |
| 24 |
would be much more likely to require webkit-gtk , yes? |
| 25 |
|
| 26 |
So a KDE user, with USE="-gstreamer" , is most likely not going to run |
| 27 |
into this issue yes? And Gnome users that have webkit-gtk[gstreamer] |
| 28 |
packages don't run into this issue with chromium anyways, right? |
| 29 |
|
| 30 |
(i know there's always overlap as anyone can install anything, but i'm |
| 31 |
thinking of the general scope of impact here) |
| 32 |
|
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 35 |
|
| 36 |
iF4EAREIAAYFAk/+1m0ACgkQ2ugaI38ACPBgQwD8DuLYiLZv4LUAuW1VACqRW/av |
| 37 |
npl1U7DXm8jqPM4l0B4BALR4FY+yUD824X2+UwbB6hAjEZrYpLSIQz2zINbUiLYK |
| 38 |
=vYhV |
| 39 |
-----END PGP SIGNATURE----- |
Archives