Ankur Sinha via rpmfusion-developers wrote:
>> That said, Chromium also uses a bundled OpenH264 to encode H.264 for
>> WebRTC. If that is not patched to support dlopening, then we still need a
>> qt6- qtwebengine-freeworld built with the bundled OpenH264 enabled. We
>>
Ankur Sinha via rpmfusion-developers wrote:
> I upgraded here, so maybe I've done this in the past and it's still
> there. I see this in my qutebrowser config:
>
> ```
> ppapi-widevine-path=/opt/google/chrome/libwidevinecdm.so
> ```
So you have the proprietary google-chrome installed? That includ
odec name), so the list
> might not be all that wrong even in Fedora.
If there's a way to get the list or test out the supported codecs, I can
do that and report back.
> That said, Chromium also uses a bundled OpenH264 to encode H.264 for WebRTC.
> If that is not patched to su
n in Fedora.
That said, Chromium also uses a bundled OpenH264 to encode H.264 for WebRTC.
If that is not patched to support dlopening, then we still need a qt6-
qtwebengine-freeworld built with the bundled OpenH264 enabled. We are not
allowed to ship OpenH264 directly in Fedora, only through
Hi Kevin,
On Tue, Sep 26, 2023 12:56:04 +0200, Kevin Kofler via rpmfusion-developers
wrote:
> Ankur Sinha via rpmfusion-developers wrote:
> > No freeworld package is needed for qt6-qtwebengine. It is linked
> > against Fedora's system ffmpeg and will gracefully upgrade when
> > libavcodec-freewor
Ankur Sinha via rpmfusion-developers wrote:
> No freeworld package is needed for qt6-qtwebengine. It is linked
> against Fedora's system ffmpeg and will gracefully upgrade when
> libavcodec-freeworld is installed.
It will pick up the FFmpeg library, yes, but will it actually report the
proper lis
Hi folks,
No -freeworld package is required for qt6-qtwebengine. Neal said:
"
No freeworld package is needed for qt6-qtwebengine. It is linked
against Fedora's system ffmpeg and will gracefully upgrade when
libavcodec-freeworld is installed.
"
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He /
On Thu, Sep 21, 2023 10:33:04 +0200, Nicolas Chauvet wrote:
> Hi Ankur,
Hi Nicolas,
> Thanks for raising this point here.
>
> My understanding is that qt6-qtwebengine doesn't have the restriction
> experienced with the qt5 counterpart wrt runtime codec detection.
> So we should be able to use th
so do we need to have a
> qt6-qtwebengine-freeworld in RPM Fusion too now?
>
> As always, I'm happy to help with the rebuilds etc., but I don't know
> enough about Qt development to do the initial packaging.
Hi Ankur,
Thanks for raising this point here.
My understanding is that
Hi folks,
Upgraded to F39 a few days ago and got the new Qutebrowser 3.0.0 update
today. It asked me if I wanted to use Qt5 or Qt6. I see there's a
qt6-qtwebengine in Fedora now, so do we need to have a
qt6-qtwebengine-freeworld in RPM Fusion too now?
As always, I'm happy to hel
10 matches
Mail list logo