On 12/07/12 12:17 AM, Ben de Groot wrote:
> On 12 July 2012 06:51, Zac Medico <zmedico@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 ?
On 12/07/12 07:41 AM, Ben de Groot wrote:
> On 12 July 2012 17:52, Rich Freeman <rich0@gentoo.org> wrote:
>> On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot
>> <yngwin@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)
On 12 July 2012 21:51, Ian Stakenvicius <axs@gentoo.org> wrote:
> -----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 <rich0@gentoo.org> wrote:
>>> On Thu, Jul 12, 2012 at 12:17 AM, Ben de Groot
>>> <yngwin@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?
None.
> I figured that gnome stuffs would be much more likely to require webkit-gtk , yes?
Indeed.
> 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)
Correct.
A KDE user with -gstreamer -icu set, should not have problems. But
once gstreamer is set for HTML5 audio/video support (which qt-webkit
enables by default on users request), the problem with -icu blocking
chromium appears. I still have no idea how many Qt (including KDE)
users also want chromium though.
For the time being we have decided to leave the useflag defaults as-is.
I have added a new part to our FAQ on the wiki, so users can be pointed to that:
Portage Output / End User Experience
