From: Saul Wold <sgw@linux.intel.com>
To: Andrei Gherzan <andrei@gherzan.ro>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2][ 1/2] libav: Add v9.10
Date: Thu, 05 Dec 2013 11:53:23 -0800 [thread overview]
Message-ID: <52A0D9B3.10107@linux.intel.com> (raw)
In-Reply-To: <1386234101-21411-1-git-send-email-andrei@gherzan.ro>
On 12/05/2013 01:01 AM, Andrei Gherzan wrote:
> This version includes libavresample needed for packages like xbmc.
> To use this version add:
> PREFERRED_VERSION_libav = "9.10".
> Removed git version as being an older version of a 9.X release.
>
> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> ---
> .../libav/{libav_git.bb => libav_9.10.bb} | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
> rename meta/recipes-multimedia/libav/{libav_git.bb => libav_9.10.bb} (65%)
>
> diff --git a/meta/recipes-multimedia/libav/libav_git.bb b/meta/recipes-multimedia/libav/libav_9.10.bb
> similarity index 65%
> rename from meta/recipes-multimedia/libav/libav_git.bb
> rename to meta/recipes-multimedia/libav/libav_9.10.bb
> index 951baa9..a76cc9c 100644
> --- a/meta/recipes-multimedia/libav/libav_git.bb
> +++ b/meta/recipes-multimedia/libav/libav_9.10.bb
> @@ -1,16 +1,13 @@
> require libav.inc
>
> -LIC_FILES_CHKSUM = "file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> - file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 \
> - file://COPYING.LGPLv2.1;md5=bd7a443320af8c812e4c18d1b79df004 \
> - file://COPYING.LGPLv3;md5=e6a600fd5e1d9cbde2d983680233ad02"
> +SRC_URI = "http://libav.org/releases/libav-9.10.tar.xz"
>
why not use ${BP} here instead, so we do not need to edit it for version
changes?
> -PV = "9.8+git${SRCPV}"
> +SRC_URI[md5sum] = "4b49d1d8734815ca095bb0600d41c5cb"
> +SRC_URI[sha256sum] = "83dbe640779da1c1e8d8836c99575f57f749d18407494ebca451578afee9300d"
>
> DEFAULT_PREFERENCE = "-1"
>
> -SRCREV = "9aaca159bd220582c698f13d081a455f398c9975"
> -SRC_URI = "git://git.libav.org/libav.git"
> -
> -S = "${WORKDIR}/git"
> -
> +LIC_FILES_CHKSUM = "file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> + file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 \
> + file://COPYING.LGPLv2.1;md5=bd7a443320af8c812e4c18d1b79df004 \
> + file://COPYING.LGPLv3;md5=e6a600fd5e1d9cbde2d983680233ad02"
>
LIC_FILES_CHKSUM should be at the beginning before the SRC_URI
Thanks
Sau!
prev parent reply other threads:[~2013-12-05 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 9:01 [PATCH V2][ 1/2] libav: Add v9.10 Andrei Gherzan
2013-12-05 9:01 ` [PATCH V2][ 2/2] libav: Update to v0.8.9 Andrei Gherzan
2013-12-05 19:25 ` Saul Wold
2013-12-07 18:01 ` Andrei Gherzan
2013-12-05 19:53 ` Saul Wold [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=52A0D9B3.10107@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=andrei@gherzan.ro \
--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.