Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] libav: Add v9.10
Date: Wed, 4 Dec 2013 20:07:21 +0100	[thread overview]
Message-ID: <20131204190721.GK3714@jama> (raw)
In-Reply-To: <2780723.Eg1JlMHale@helios>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

On Wed, Dec 04, 2013 at 06:57:20PM +0000, Paul Eggleton wrote:
> On Wednesday 04 December 2013 20:46:50 Andrei Gherzan wrote:
> > This version includes libavresample needed for packages like xbmc.
> > To use this version add:
> > PREFERRED_VERSION_libav = "9.10".
> 
> We really want to avoid having too many versions of the same recipe hanging 
> around. However, it seems premature to drop 0.8.x at this point. Perhaps we 
> should drop the libav_git recipe that we currently have, since that is just 
> pointing at an old 0.9.x version?
> 
> Anyone have any thoughts on this?

Or update it to point to newer (or the same revision as 9.10)

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-12-04 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 18:46 [PATCH 1/2] libav: Add v9.10 Andrei Gherzan
2013-12-04 18:46 ` [PATCH 2/2] libav: Update to v0.8.9 Andrei Gherzan
2013-12-04 18:57 ` [PATCH 1/2] libav: Add v9.10 Paul Eggleton
2013-12-04 19:07   ` Martin Jansa [this message]
2013-12-04 20:08   ` Andrei Gherzan

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=20131204190721.GK3714@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox