From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.linuxtogo.org>
Subject: Re: [PATCH] pigz: Update to upstream version 2.2.5
Date: Thu, 09 Aug 2012 16:58:21 +0300 [thread overview]
Message-ID: <5023C1FD.5040506@linux.intel.com> (raw)
In-Reply-To: <20120809071713.GA26150@giant>
On 08/09/2012 10:17 AM, Björn Stenberg wrote:
> ---
> meta/recipes-extended/pigz/pigz_2.2.4.bb | 11 -----------
> meta/recipes-extended/pigz/pigz_2.2.5.bb | 11 +++++++++++
> 2 files changed, 11 insertions(+), 11 deletions(-)
> delete mode 100644 meta/recipes-extended/pigz/pigz_2.2.4.bb
> create mode 100644 meta/recipes-extended/pigz/pigz_2.2.5.bb
>
> diff --git a/meta/recipes-extended/pigz/pigz_2.2.4.bb b/meta/recipes-extended/pigz/pigz_2.2.4.bb
> deleted file mode 100644
> index e76c49c..0000000
> --- a/meta/recipes-extended/pigz/pigz_2.2.4.bb
> +++ /dev/null
> @@ -1,11 +0,0 @@
> -require pigz.inc
> -
> -PR = "r2"
> -
> -NATIVE_PACKAGE_PATH_SUFFIX = "/${PN}"
> -
> -BBCLASSEXTEND = "native"
> -
> -SRC_URI[md5sum] = "9df2a3c742524446fa4e797c17e8fd85"
> -SRC_URI[sha256sum] = "7e7967c47f66c07be97cbfa25c8816b72f9d35258466ea31eddc7666c914160e"
> -LIC_FILES_CHKSUM = "file://pigz.c;md5=53f47c097bbf11b937a421b1816a8dc5"
> diff --git a/meta/recipes-extended/pigz/pigz_2.2.5.bb b/meta/recipes-extended/pigz/pigz_2.2.5.bb
> new file mode 100644
> index 0000000..36669c2
> --- /dev/null
> +++ b/meta/recipes-extended/pigz/pigz_2.2.5.bb
> @@ -0,0 +1,11 @@
> +require pigz.inc
> +
> +NATIVE_PACKAGE_PATH_SUFFIX = "/${PN}"
> +
> +BBCLASSEXTEND = "native"
> +
> +SRC_URI[md5sum] = "188f769ccedc403893d03049ad31e969"
> +SRC_URI[sha256sum] = "e37498cbf3a475d7ebe2519751188c29564bf8dd27ba68bd3c7fe1ac08792759"
> +LIC_FILES_CHKSUM = "file://pigz.c;md5=ee5481b3699dcac1f63cec8d038ada8a"
>
I did not catch this the first time, the md5 has changed for
LIC_FILES_CHKSUM, why? Please include a commit message as to what
changed? Even if it's just the year, we would like to track License
changes.
Also, I guess that we should really have beginline/endline for pigz.c
since we don't want to track the whole file.
Thanks
Sau!
next prev parent reply other threads:[~2012-08-09 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 15:06 [PATCH] pigz: Update to upstream version 2.2.5 Björn Stenberg
2012-08-08 16:49 ` Koen Kooi
2012-08-09 7:17 ` Björn Stenberg
2012-08-09 13:58 ` Saul Wold [this message]
2012-08-10 9:58 ` Björn Stenberg
2012-08-16 18:28 ` Saul Wold
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=5023C1FD.5040506@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.linuxtogo.org \
--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