From: Mark Hatle <mark.hatle@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: do all recipes really need LIC_FILES_CHKSUM?
Date: Mon, 7 Nov 2011 10:32:26 -0600 [thread overview]
Message-ID: <4EB8081A.5020501@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1111071120080.4441@localhost6.localdomain6>
On 11/7/11 10:24 AM, Robert P. J. Day wrote:
> On Mon, 7 Nov 2011, Mark Hatle wrote:
>
>> On 11/7/11 10:01 AM, Robert P. J. Day wrote:
>>>
>>> current poky ref manual seems pretty adamant about need for
>>> LIC_FILES_CHKSUM:
>>>
>>> "Note that this variable is mandatory for all recipes, unless the
>>> LICENSE variable is set to "CLOSED".
>>>
>>> but there's at least one counter-example,
>>> meta-demoapps/recipes-graphics/pong-clock/pong-clock_1.0.bb:
>>
>> Bug in the example.. it should be fixed.
I'm not surprised that meta-demoapps is missing this stuff.. AFAIK the stuff
here isn't run though the normal build/QA process.
If this information isn't deprecated as Gary thought it might be... then it
absolutely should be fixed.
> oooookay, but it's really not hard to find more examples like that,
> such as meta-demoapps/recipes-graphics/libxklavier/libxklavier_3.9.bb:
>
> DESCRIPTION = "Utility library to make using XKB easier"
> SECTION = "x11/libs"
> DEPENDS = "iso-codes libxml2 glib-2.0 libxkbfile"
> LICENSE = "LGPL"
> PR = "r2"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/gswitchit/libxklavier-${PV}.tar.bz2 \
> file://pkgconfigfix.patch;patch=1"
>
> inherit autotools
>
> or "xournal" in the same directory, etc, etc. i'm not trying to be
> annoyingly pedantic (he lied), just pointing out the inconsistencies.
>
> rday
>
prev parent reply other threads:[~2011-11-07 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 16:01 do all recipes really need LIC_FILES_CHKSUM? Robert P. J. Day
2011-11-07 16:06 ` Gary Thomas
2011-11-07 16:06 ` Mark Hatle
2011-11-07 16:24 ` Robert P. J. Day
2011-11-07 16:32 ` Mark Hatle [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=4EB8081A.5020501@windriver.com \
--to=mark.hatle@windriver.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@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.