From: akuster808 <akuster808@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] RFC: libav vs. ffmpeg, redux
Date: Thu, 09 Jul 2015 07:57:07 -0700 [thread overview]
Message-ID: <559E8BC3.2060300@gmail.com> (raw)
In-Reply-To: <2219152.1ss8pFxefq@peggleto-mobl.ger.corp.intel.com>
On 07/09/2015 03:24 AM, Paul Eggleton wrote:
> Hi all,
>
> A few years ago we made the switch from ffmpeg to libav (a mostly drop-in
> compatible fork), with fairly good justification at the time. However, it looks
> like Debian has just made the switch back to ffmpeg, citing a number of reasons
> - most notably more responsive security issue patching in recent history.
> Here's a page with their full reasoning:
>
> https://wiki.debian.org/Debate/libav-provider/ffmpeg
>
> Gstreamer (gst-libav, specifically) has also just recently made the switch back
> for its internal copy:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=751607
>
> What do people think? Should we be looking to make the switch back in OE as
> well?
>
That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so
the change which will simplify things too.
- armin
> Cheers,
> Paul
>
WARNING: multiple messages have this Message-ID (diff)
From: akuster808 <akuster808@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: RFC: libav vs. ffmpeg, redux
Date: Thu, 09 Jul 2015 07:57:07 -0700 [thread overview]
Message-ID: <559E8BC3.2060300@gmail.com> (raw)
In-Reply-To: <2219152.1ss8pFxefq@peggleto-mobl.ger.corp.intel.com>
On 07/09/2015 03:24 AM, Paul Eggleton wrote:
> Hi all,
>
> A few years ago we made the switch from ffmpeg to libav (a mostly drop-in
> compatible fork), with fairly good justification at the time. However, it looks
> like Debian has just made the switch back to ffmpeg, citing a number of reasons
> - most notably more responsive security issue patching in recent history.
> Here's a page with their full reasoning:
>
> https://wiki.debian.org/Debate/libav-provider/ffmpeg
>
> Gstreamer (gst-libav, specifically) has also just recently made the switch back
> for its internal copy:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=751607
>
> What do people think? Should we be looking to make the switch back in OE as
> well?
>
That make sense to me. Also libav has LICENSE_FLAGS = "commercial" so
the change which will simplify things too.
- armin
> Cheers,
> Paul
>
next prev parent reply other threads:[~2015-07-09 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:24 RFC: libav vs. ffmpeg, redux Paul Eggleton
2015-07-09 10:30 ` [OE-core] " Burton, Ross
2015-07-09 10:30 ` Burton, Ross
2015-07-09 10:35 ` [OE-core] " Christian Ege
2015-07-09 11:41 ` Burton, Ross
2015-07-09 11:41 ` [oe] " Burton, Ross
2015-07-09 14:57 ` akuster808 [this message]
2015-07-09 14:57 ` akuster808
2015-07-09 15:02 ` [OE-core] " Burton, Ross
2015-07-09 15:02 ` [oe] " Burton, Ross
2015-07-11 5:46 ` [OE-core] " Khem Raj
2015-07-11 5:46 ` [oe] " Khem Raj
2015-07-10 14:19 ` Koen Kooi
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=559E8BC3.2060300@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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.
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.