From: Mike Looijmans <mike.looijmans@topic.nl>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?
Date: Tue, 8 Sep 2015 12:19:51 +0200 [thread overview]
Message-ID: <55EEB647.7000101@topic.nl> (raw)
In-Reply-To: <CAHiDW_GPgMLsLbASU4qHCHY65E9OWK3G3BgTpq=vAd8tsPDNbg@mail.gmail.com>
On 08-09-15 10:44, Jussi Kukkonen wrote:
> On 7 September 2015 at 19:38, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
> On 07-09-15 13:56, Jussi Kukkonen wrote:
>
> On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>
> <mailto:mike.looijmans@topic.nl <mailto:mike.looijmans@topic.nl>>> wrote:
>
> Just sped another hour or so trying to pinpoint this, but I cannot
> wrap my head around it. What do I have to do to add a license to a
> layer without these annoying warnings?
>
>
> I just tried this (with master branch) and it seems to work fine
> here... Are you using master or something older?
>
>
> Did you try that in a separate, empty layer? I suspect I'm missing a
> variable or directive of some kind which cause it to miss the license file.
>
>
> I have layer with literally only:
> * conf/layer.conf file with just LICENSE_PATH += "${LAYERDIR}/licenses"
> * licenses/internal file
> This layer is added to BBLAYERS. After this a recipe from another layer seems
> to be able to use the "internal" license...
The warning doesn't appear until you actually build a rootfs with that package
in it.
>
> Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file
> when you build the recipe for BPN?
>
>
> Nope.
Ah, wait, on closer inspection it actually exists, but it's a symlink to some
none-existing location. Apparently, to save some diskspace and reduce
maintenance on text files I linked a few files together. Somehow, the link got
copied instead of the file contents.
I un-symlinked the "internal" file, and (together with some forced rebuilds)
that finally made the warning go away.
Thanks!
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-09-08 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 7:23 Getting rid of "The license listed internal was not in the licenses collected" warnings? Mike Looijmans
2015-09-07 10:14 ` Mike Looijmans
2015-09-07 11:56 ` Jussi Kukkonen
2015-09-07 16:38 ` Mike Looijmans
2015-09-08 8:44 ` Jussi Kukkonen
2015-09-08 10:19 ` Mike Looijmans [this message]
2015-09-08 10:39 ` Mikko.Rapeli
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=55EEB647.7000101@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=jussi.kukkonen@intel.com \
--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