From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, ulf@emagii.com
Subject: Re: Change in "openembedded-core/meta/files/common-licenses/LGPL-2.0" breaks opie-image
Date: Fri, 09 Dec 2011 10:40:35 +0000 [thread overview]
Message-ID: <6586493.ofj4pSsnLf@helios> (raw)
In-Reply-To: <4EE1E350.4010304@emagii.com>
On Friday 09 December 2011 11:30:40 Ulf Samuelsson wrote:
> I think someone needs to sit down and do this in a structured manner.
> A number of license files were modified.
> For each file, the old checksum needs to be searched for in the tree,
> and the license modified.
In case it wasn't clear I'm actually doing something which is not recommended
in meta-opie since it provides none of the protection of LIC_FILES_CHKSUM and
no small amount of fragility, as we have discovered. Nobody should really be
doing this if they can possibly avoid it, and if they are then they shouldn't
be too surprised when things break.
FWIW, none of the recipes in OE-core itself (nor meta-oe for that matter)
refer to files in the common license directory - I just checked.
> A grep for "LICENSE =" should reveal offending recipes with "<recipe1>
> && <recipe2>"
> or "<recipe1>/<recipe2>" etc.
This is a separate issue.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-09 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 10:09 Change in "openembedded-core/meta/files/common-licenses/LGPL-2.0" breaks opie-image Ulf Samuelsson
2011-12-09 10:17 ` Ulf Samuelsson
2011-12-09 10:24 ` Paul Eggleton
2011-12-09 10:30 ` Ulf Samuelsson
2011-12-09 10:40 ` Paul Eggleton [this message]
2011-12-09 19:03 ` Flanagan, Elizabeth
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=6586493.ofj4pSsnLf@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.com \
/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