all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: icecat: Add ffmpeg support.
Date: Tue, 10 Jan 2017 18:51:35 -0500	[thread overview]
Message-ID: <87tw96fp88.fsf@netris.org> (raw)
In-Reply-To: <87vatnq9pj.fsf@gmail.com> (Mathieu OTHACEHE's message of "Tue, 10 Jan 2017 15:19:04 +0100")

Mathieu OTHACEHE <m.othacehe@gmail.com> writes:

>> Have you tried installing 'gst-libav' in your profile?  That's what I
>> do, and I'm able to watch videos in icecat that use those codecs.
>
> Yes I tried but I'm still not able to read videos from dailymotion or
> vimeo for instance. With this patch, it seems to work.
>
> Youtube also report support for H.264 and MSE & H.264 is problematic
> with current icecat (with or without gst-libav), but working with this
> patch.
>
> See: https://www.youtube.com/html5
>
> Do you share the same observations ?

Indeed, you're right.  For some reason, our current IceCat package
doesn't acknowledge the existence of the H.264 decoder in gst-libav,
although 'totem' is able to play such files via gstreamer and gst-libav.

It would be preferable to find out why the gstreamer approach is not
working properly.  I see at least three disadvantages of depending on
ffmpeg directly:

1. Every time ffmpeg is updated, IceCat would need to be recompiled.

2. Users who wish to avoid codecs under threat by patent holders would
   have no easy recourse, whereas currently they can simply avoid
   installing 'gst-libav'.

3. Supporting all of the codecs in ffmpeg entails a security risk,
   because it contains a large number of codecs, some of which surely
   have security flaws.  An attacker can find an obscure codec in there
   that nobody uses and exploit it.  At present, users can greatly
   mitigate this risk by installing only 'gst-plugins-good'.

For multiple reasons, it would be best to isolate patent-encumbered
codecs to optional plugins, rather than "baking them in" to our
packages.

What do you think?

Thank you for looking into this.

       Mark

      reply	other threads:[~2017-01-10 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 21:28 [PATCH] gnu: icecat: Add ffmpeg support Mathieu OTHACEHE
2017-01-09 21:56 ` Danny Milosavljevic
2017-01-10  0:38 ` Mark H Weaver
2017-01-10 14:19   ` Mathieu OTHACEHE
2017-01-10 23:51     ` Mark H Weaver [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tw96fp88.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.