| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 12/07/12 12:17 AM, Ben de Groot wrote: |
| 5 |
> On 12 July 2012 06:51, Zac Medico <zmedico@g.o> wrote: |
| 6 |
>> |
| 7 |
>> Here's another related bug report, specifically about the solving |
| 8 |
>> the libxml2/qt-webkit/chromium conflict: |
| 9 |
>> |
| 10 |
>> https://bugs.gentoo.org/show_bug.cgi?id=426222 |
| 11 |
>> |
| 12 |
>> -- |
| 13 |
> |
| 14 |
> Actually, there is another workable solution, and that is to set |
| 15 |
> USE="-gstreamer -icu" for qt-webkit. |
| 16 |
> |
| 17 |
> Currently we enable gstreamer by default in the ebuild (as it is |
| 18 |
> used for HTML5 audio/video, which is expected functionality in |
| 19 |
> qt-webkit based web browsers etc.), but we are considering if we |
| 20 |
> should perhaps not enable this by default. |
| 21 |
> |
| 22 |
|
| 23 |
Would the conflict go away if the rdeps of qt-webkit (these browsers) |
| 24 |
still had a use dep on gstreamer? IE, do these browsers tend to be |
| 25 |
installed even though the user's installed/installing chromium ? |
| 26 |
|
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 29 |
|
| 30 |
iF4EAREIAAYFAk/+04gACgkQ2ugaI38ACPDRUAD+MgphaweWeoPKBrZEJRY3LsTK |
| 31 |
pfBUoCujOvXgicioP4EA/18m849xCRC3lXrjF1fbKBurQuqt56zvk5HQ/kWbhAlC |
| 32 |
=6EZF |
| 33 |
-----END PGP SIGNATURE----- |
Archives