From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 06/12] libav: 9.18 -> 11.4
Date: Mon, 15 Jun 2015 13:35:26 +0800 [thread overview]
Message-ID: <557E641E.5040300@windriver.com> (raw)
In-Reply-To: <CAJTo0LZ1eNH8KScAf=3bJbGGVFV=OCU5GXodPp8=LMVc34pAJQ@mail.gmail.com>
On 06/12/2015 07:11 PM, Burton, Ross wrote:
>
> On 12 June 2015 at 09:40, Paul Eggleton <paul.eggleton@linux.intel.com
> <mailto:paul.eggleton@linux.intel.com>> wrote:
>
> I didn't talk to Richard about it but I think there may have been some
> discussion on this list about the possibility of 9->10->11 breaking API
> compatibility with applications. Did you do testing with recipes in meta-
> oe/meta-multimedia that depend upon libav?
>
>
> Yes, that's exactly why I didn't merge it into MUT: more research needed as this
> upgrade was proposed by Kai a few weeks back and there was a discussion there.
>
> I wasn't rejecting the upgrade, just needed a good look and didn't get around to
> it yet. The big question is upgrade path: does everything in oe-core still
> build, and is there a sufficient amount of recipes outside of oe-core using
> libav 9 that we should keep it around?
I've tested all oe-core's related recipes with set commercial license flags,
but didn't test the recipes outside of oe-core, I will test the recipes in
meta-oe/meta-multimedia.
// Robert
>
> Ross
next prev parent reply other threads:[~2015-06-15 5:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 14:51 [PATCH 00/12] Packages Upgrade Robert Yang
2015-06-09 14:51 ` [PATCH 01/12] libpfm4: 4.3.0 -> 4.6.0 Robert Yang
2015-06-09 14:51 ` [PATCH 02/12] clutter-gst-3.0: 3.0.4 -> 3.0.6 Robert Yang
2015-06-09 14:51 ` [PATCH 03/12] augeas: 1.2.0 -> 1.4.0 Robert Yang
2015-06-09 14:51 ` [PATCH 04/12] dropbear: 2014.66 -> 2015.67 Robert Yang
2015-06-09 14:51 ` [PATCH 05/12] gpgme: 1.4.3 -> 1.5.4 Robert Yang
2015-06-09 14:51 ` [PATCH 06/12] libav: 9.18 -> 11.4 Robert Yang
2015-06-12 3:19 ` Robert Yang
2015-06-12 8:40 ` Paul Eggleton
2015-06-12 11:11 ` Burton, Ross
2015-06-15 5:35 ` Robert Yang [this message]
2015-06-09 14:51 ` [PATCH 07/12] gstreamer1.0-libav: fix build for i586 with gcc Robert Yang
2015-06-09 14:51 ` [PATCH 08/12] qmmp: 0.7.7 -> 0.8.5 Robert Yang
2015-06-09 14:51 ` [PATCH 09/12] libevdev: 1.3 -> 1.4.2 Robert Yang
2015-06-09 14:51 ` [PATCH 10/12] blktrace: 1.0.5 -> 1.1.0 Robert Yang
2015-06-09 16:50 ` Burton, Ross
2015-06-10 1:45 ` Robert Yang
2015-06-09 14:51 ` [PATCH 11/12] yasm: 1.2.0 -> 1.3.0 Robert Yang
2015-06-09 14:51 ` [PATCH 12/12] x264: r2265 -> r2491 Robert Yang
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=557E641E.5040300@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox