From: Mike Looijmans <mike.looijmans@topic.nl>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: WARNING: The license listed CLOSED was not in the licenses collected for foo
Date: Tue, 12 May 2015 08:03:04 +0200 [thread overview]
Message-ID: <55519798.1000909@topic.nl> (raw)
In-Reply-To: <1756352.ngOcR97Dgu@peggleto-mobl.ger.corp.intel.com>
On 11-05-15 11:09, Paul Eggleton wrote:
> If you want to do this you need to add a generic license file for the license
> in question, which means extending LICENSE_PATH in your custom layer to a
> directory containing a file named with the license.
I did that, but it didn't get rid of the warning message (see previous post).
> You're right that the error message isn't as helpful as it could be. We should
> fix that as well.
Well if I knew what to do myself, I could provide a patch for that...
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2015-05-12 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 11:07 WARNING: The license listed CLOSED was not in the licenses collected for foo Steffen Sledz
2015-05-08 12:39 ` Paul Eggleton
2015-05-08 12:40 ` Otavio Salvador
2015-05-08 12:47 ` Paul Eggleton
2015-05-11 6:54 ` Mike Looijmans
2015-05-11 8:58 ` Mike Looijmans
2015-05-11 9:36 ` Paul Eggleton
2015-05-11 9:39 ` Mike Looijmans
2015-05-11 9:09 ` Paul Eggleton
2015-05-12 6:03 ` Mike Looijmans [this message]
2015-05-13 10:59 ` Steffen Sledz
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=55519798.1000909@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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