All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: proposal: let's move oe-core to ffmpeg (from libav)
Date: Thu, 21 Jan 2016 17:14:28 +0200	[thread overview]
Message-ID: <56A0F5D4.5090701@linux.intel.com> (raw)

Hello,

let's replace libav with ffmpeg in oe-core. The reasons are:

- all of the major distributions are using ffmpeg now (the last holdout 
was Debian, and they switched to ffmpeg in summer 2015 after a long 
discussion and deliberation [1][2])
- ffmpeg is much more responsive to security issues
- ffmpeg does regular releases, while libav hasn't had one since spring 2015
- other reasons listed in [2]

[1] https://lwn.net/Articles/650816/
[2] https://wiki.debian.org/Debate/libav-provider/ffmpeg

Objections, thoughts?


Alex


             reply	other threads:[~2016-01-21 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 15:14 Alexander Kanavin [this message]
2016-01-21 15:40 ` [OE-core] proposal: let's move oe-core to ffmpeg (from libav) Burton, Ross
2016-01-21 15:40   ` Burton, Ross
2016-01-21 17:55   ` [OE-core] " Paul Eggleton
2016-01-21 17:55     ` [oe] " Paul Eggleton

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=56A0F5D4.5090701@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.