From: Saul Wold <saul.wold@intel.com>
To: Mei Lei <lei.mei@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 06/20] python-imaging:Add license checksum to bb file
Date: Thu, 25 Nov 2010 10:50:26 -0800 [thread overview]
Message-ID: <4CEEAFF2.2060109@intel.com> (raw)
In-Reply-To: <95222fd970206dcb220b03fa06499ab5027d0db9.1290681886.git.lei.mei@intel.com>
On 11/24/2010 09:05 PM, Mei Lei wrote:
> Add README file checksum to bb file
>
> Signed-off-by: Mei Lei<lei.mei@intel.com>
> ---
> .../python/python-imaging_1.1.7.bb | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/python/python-imaging_1.1.7.bb b/meta/recipes-devtools/python/python-imaging_1.1.7.bb
> index 9812043..5319758 100644
> --- a/meta/recipes-devtools/python/python-imaging_1.1.7.bb
> +++ b/meta/recipes-devtools/python/python-imaging_1.1.7.bb
> @@ -2,6 +2,7 @@ DESCRIPTION = "Python Imaging Library"
> SECTION = "devel/python"
> PRIORITY = "optional"
> LICENSE = "GPL"
Mei,
Is this really GPL? Please update this to correctly.
Sau!
> +LIC_FILES_CHKSUM = "file://README;beginline=92;endline=120;md5=c4371af4579f1e489cf881c1443dd4ec"
> DEPENDS = "freetype jpeg tiff"
> RDEPENDS = "python-lang python-stringold"
> SRCNAME = "Imaging"
next prev parent reply other threads:[~2010-11-25 18:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:44 [PATCH 00/20]Add 20 recipes license file MD5sum information Mei Lei
2010-11-25 2:25 ` [PATCH 01/20] mpfr:Add license checksum and update the GPL information Mei Lei
2010-11-25 3:22 ` [PATCH 02/20] perl:Add license checksum to bb file Mei Lei
2010-11-25 4:25 ` [PATCH 03/20] prelink:Add " Mei Lei
2010-11-25 4:30 ` [PATCH 04/20] python:Add " Mei Lei
2010-11-25 5:03 ` [PATCH 05/20] python-dbus:Add " Mei Lei
2010-11-25 5:05 ` [PATCH 06/20] python-imaging:Add " Mei Lei
2010-11-25 18:50 ` Saul Wold [this message]
2010-11-25 5:29 ` [PATCH 07/20] python-pygobject:Add license checksum and update the GPL information Mei Lei
2010-11-25 5:34 ` [PATCH 08/20] python-pygtk:Add " Mei Lei
2010-11-25 5:41 ` [PATCH 09/20] python-pyrex:Add license checksum and update the License information Mei Lei
2010-11-25 5:48 ` [PATCH 10/20] python-scons:Add license checksum and update the GPL information Mei Lei
2010-11-25 5:51 ` [PATCH 11/20] quilt:Add " Mei Lei
2010-11-25 6:50 ` [PATCH 12/20] make:Add " Mei Lei
2010-11-25 7:00 ` [PATCH 13/20] lsof:Add license checksum to bb file Mei Lei
2010-11-25 9:08 ` [PATCH 14/20] dtc:Add license checksum and add the GPL information Mei Lei
2010-11-25 9:34 ` [PATCH 15/20] libtheora:Add license checksum to bb file Mei Lei
2010-11-25 9:46 ` [PATCH 16/20] libxml-simple-perl:Add " Mei Lei
2010-11-25 9:48 ` [PATCH 17/20] mc:Add " Mei Lei
2010-11-25 9:50 ` [PATCH 18/20] qmmp:Add " Mei Lei
2010-11-25 10:41 ` [PATCH 20/20] flex:Add license checksum and add the license information Mei Lei
2010-11-25 10:41 ` [PATCH 19/20] base-files:Add license checksum to bb file Mei Lei
2010-12-02 18:02 ` [PATCH 00/20]Add 20 recipes license file MD5sum information Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2010-11-26 1:33 [PATCH 00/20]Update the python-imaging license information Mei Lei
2010-11-26 1:28 ` [PATCH 06/20] python-imaging:Add license checksum to bb file Mei Lei
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=4CEEAFF2.2060109@intel.com \
--to=saul.wold@intel.com \
--cc=lei.mei@intel.com \
--cc=poky@yoctoproject.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.