-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/07/12 12:17 AM, Ben de Groot wrote: > On 12 July 2012 06:51, Zac Medico <zmed...@gentoo.org> wrote: >> >> Here's another related bug report, specifically about the solving >> the libxml2/qt-webkit/chromium conflict: >> >> https://bugs.gentoo.org/show_bug.cgi?id=426222 >> >> -- > > 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. >
Would the conflict go away if the rdeps of qt-webkit (these browsers) still had a use dep on gstreamer? IE, do these browsers tend to be installed even though the user's installed/installing chromium ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAk/+04gACgkQ2ugaI38ACPDRUAD+MgphaweWeoPKBrZEJRY3LsTK pfBUoCujOvXgicioP4EA/18m849xCRC3lXrjF1fbKBurQuqt56zvk5HQ/kWbhAlC =6EZF -----END PGP SIGNATURE-----