Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster@mvista.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] V2 lz4: update to latest version
Date: Wed, 16 Jul 2014 10:11:20 +0100	[thread overview]
Message-ID: <1405501880.20402.17.camel@ted> (raw)
In-Reply-To: <1405388483-30716-1-git-send-email-akuster@mvista.com>

On Mon, 2014-07-14 at 18:41 -0700, Armin Kuster wrote:
> update to version r119
> Use github instead of svn

I'm still a little concerned about this change from svn to git. Which is
the definitive source? It looks like the svn repo is active too?

I just don't want to end up in a position where we're pulling from
someone's hack'n'dev version of lz4 rather than the place considered the
real "master" source...

Cheers,

Richard


> LICENSE md5sum changed since it was updated in r117
> FIxes CVE-2014-4611
> 
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
>  meta/recipes-support/lz4/lz4_git.bb | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 meta/recipes-support/lz4/lz4_git.bb
> 
> diff --git a/meta/recipes-support/lz4/lz4_git.bb b/meta/recipes-support/lz4/lz4_git.bb
> new file mode 100644
> index 0000000..3978d76
> --- /dev/null
> +++ b/meta/recipes-support/lz4/lz4_git.bb
> @@ -0,0 +1,18 @@
> +SUMMARY = "Extremely Fast Compression algorithm"
> +DESCRIPTION = "LZ4 is a very fast lossless compression algorithm, providing compression speed at 400 MB/s per core, scalable with multi-cores CPU. It also features an extremely fast decoder, with speed in multiple GB/s per core, typically reaching RAM speed limits on multi-core systems."
> +
> +LICENSE = "BSD"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=0b0d063f37a4477b54af2459477dcafd"
> +
> +SRCREV = "28fd251bc7b42e5cde15f9a2d78fc53b3b575558"
> +SRC_URI= "git://github.com/Cyan4973/lz4.git;branch=master"
> +
> +S = "${WORKDIR}/git"
> +
> +EXTRA_OEMAKE = "PREFIX=${prefix} CC='${CC}' DESTDIR=${D} LIBDIR=${libdir} INCLUDEDIR=${includedir}"
> +
> +do_install() {
> +	oe_runmake install
> +}
> +
> +BBCLASSEXTEND += "native nativesdk"
> -- 
> 1.9.1
> 




  parent reply	other threads:[~2014-07-16  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  1:41 [meta-oe][PATCH] V2 lz4: update to latest version Armin Kuster
2014-07-15  5:30 ` akuster
2014-07-16  9:11 ` Richard Purdie [this message]
2014-07-16 13:48   ` Burton, Ross
2014-07-16 19:07     ` akuster

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=1405501880.20402.17.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox