ungoogled-chromium: proprietary codecs enabled?

DoneSubmitted by Giovanni Biscuolo.
Details
3 participants
  • Giovanni Biscuolo
  • Maxim Cournoyer
  • Ricardo Wurmus
Owner
unassigned
Severity
normal
G
G
Giovanni Biscuolo wrote on 21 Feb 2019 09:02
(address . bug-guix@gnu.org)(name . Luke)(address . g4jc@hyperbola.info)
87h8cx7eno.fsf@roquette.mug.biscuolo.net
Hello,

I'm forwarding this, extracted from this message

Luke <g4jc@hyperbola.info> writes:

[...]

Toggle quote (5 lines)
> Some GN prefs missing from chromium.scm:
> ---
> ;; Disable non-free codecs
> "proprietary_codecs=false"

while ungoogled-chromiun package definition now contains

Toggle snippet (5 lines)
;; Don't arbitrarily restrict formats supported by system ffmpeg.
"proprietary_codecs=true"
"ffmpeg_branding=\"Chrome\""

does this conflicts with GNU FSDG?

Thanks!
Giovanni

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlxuWwsACgkQ030Op87M
ORIMwQ//a1H7a0b1Bv0swfM8QvJH6DFJeoxlP33M58FlmwhtRgfZXQCamjzOv1oy
sffp5ZqyzSx4RdCN/IWarsrvIwvaRh3/o0BdfknDXilqrroKBlebjL570STq0IEV
G4XN7qM89qYBBP3aIip6zeS137ATblwWKi1SHMS7EGj9t9GFGd02S5aBClAlpweN
7/GddBKp8HVEqWoIf3mY/P7rRII/0xxOKzffNOEMeTMoLDAwK5RvFSJv1bRROiRY
/virMTlEDMsQSF5AHd+P27hiRQwhTMNVmW3EvagATP2GtbsMJXK9usriVXfUNO9a
5DJY9xhA/X4oSJ/wNrpHw5FdOglpIT7TUn5yzIvz8etvWo6QWwAxISFoafFCUqqx
QY7zgAno5cQxIfxUFjefXG0KDzsYwFejDGh1VJHz/GDVs5Dh+hfE2HgIJO97fl2t
Goo1WvljBWMzri1mosvLSNmZKXD717RXrVib0EHoIJslirN3hiEFpeLoNuzA6amy
JYhATu8ENJGHXGg5niAv3Ez762WBARiIZNViWP/l3j/BW+Ayu1awiEOuPSTJww2o
Ep+yJnV2pDPhFoy6tOs7P2+TfAqr65hhbiMn4VqT3V5tna3ZeM+Sn9ET3CNFWVVb
np3nAnpfm3sJ+p6YBU/+0xKVnNM747XjiwpMRLbstMygQa747MI=
=JD/J
-----END PGP SIGNATURE-----

R
R
Ricardo Wurmus wrote on 21 Feb 2019 16:50
(name . Giovanni Biscuolo)(address . g@xelera.eu)
87lg293ztx.fsf@elephly.net
Giovanni Biscuolo <g@xelera.eu> writes:

Toggle quote (24 lines)
> Hello,
>
> I'm forwarding this, extracted from this message
> http://lists.nongnu.org/archive/html/gnu-linux-libre/2019-02/msg00083.html
>
> Luke <g4jc@hyperbola.info> writes:
>
> [...]
>
>> Some GN prefs missing from chromium.scm:
>> ---
>> ;; Disable non-free codecs
>> "proprietary_codecs=false"
>
> while ungoogled-chromiun package definition now contains
>
> --8<---------------cut here---------------start------------->8---
> ;; Don't arbitrarily restrict formats supported by system ffmpeg.
> "proprietary_codecs=true"
> "ffmpeg_branding=\"Chrome\""
> --8<---------------cut here---------------end--------------->8---
>
> does this conflicts with GNU FSDG?

As far as I understand, this lets Chromium use whatever codecs are
provided by the system ffmpeg. Restrictions in codecs are up to the
ffmpeg package, not Chromium.

--
Ricardo
M
M
Maxim Cournoyer wrote on 14 Nov 2021 02:29
(name . Ricardo Wurmus)(address . rekado@elephly.net)
877ddbikxf.fsf@gmail.com
Hello,

Ricardo Wurmus <rekado@elephly.net> writes:

Toggle quote (30 lines)
> Giovanni Biscuolo <g@xelera.eu> writes:
>
>> Hello,
>>
>> I'm forwarding this, extracted from this message
>> http://lists.nongnu.org/archive/html/gnu-linux-libre/2019-02/msg00083.html
>>
>> Luke <g4jc@hyperbola.info> writes:
>>
>> [...]
>>
>>> Some GN prefs missing from chromium.scm:
>>> ---
>>> ;; Disable non-free codecs
>>> "proprietary_codecs=false"
>>
>> while ungoogled-chromiun package definition now contains
>>
>> --8<---------------cut here---------------start------------->8---
>> ;; Don't arbitrarily restrict formats supported by system ffmpeg.
>> "proprietary_codecs=true"
>> "ffmpeg_branding=\"Chrome\""
>> --8<---------------cut here---------------end--------------->8---
>>
>> does this conflicts with GNU FSDG?
>
> As far as I understand, this lets Chromium use whatever codecs are
> provided by the system ffmpeg. Restrictions in codecs are up to the
> ffmpeg package, not Chromium.

I confirm this is how it works; and that it isn't an FSDG problem. The
source now mentions ";; Do not artifically restrict formats supported by
system ffmpeg.".

Closing.

Thanks for the report!

Maxim
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 34605@debbugs.gnu.org