Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH] license: Ensure we find multilib packages also
Date: Thu, 13 Sep 2012 12:26:19 -0700	[thread overview]
Message-ID: <1347564379-14252-1-git-send-email-sgw@linux.intel.com> (raw)

Make sure to find -package, this was causing a failure
in the multi-lib build license generation during rootfs.

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 meta/classes/license.bbclass |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta/classes/license.bbclass b/meta/classes/license.bbclass
index 29fe938..b29067c 100644
--- a/meta/classes/license.bbclass
+++ b/meta/classes/license.bbclass
@@ -88,7 +88,7 @@ license_create_manifest() {
 	# list of installed packages is broken for deb
 	for pkg in ${INSTALLED_PKGS}; do
 		# not the best way to do this but licenses are not arch dependant iirc
-		filename=`ls ${TMPDIR}/pkgdata/*/runtime-reverse/${pkg}| head -1`
+		filename=`ls ${TMPDIR}/pkgdata/*/runtime-reverse/*${pkg}| head -1`
 		pkged_pn="$(sed -n 's/^PN: //p' ${filename})"
 
 		# exclude locale recipes
-- 
1.7.7.6




             reply	other threads:[~2012-09-13 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 19:26 Saul Wold [this message]
2012-09-13 22:31 ` [RFC PATCH] license: Ensure we find multilib packages also Paul Eggleton
2012-09-13 22:43   ` Saul Wold
2012-09-14 16:01     ` Richard Purdie
2012-09-14 16:48       ` Mark Hatle
2012-09-14 20:50         ` Flanagan, Elizabeth
2012-09-14 22:09           ` Richard Purdie
2012-09-14 22:11           ` Paul Eggleton
2012-09-14 22:26             ` Flanagan, Elizabeth
2012-09-14 22:31               ` Mark Hatle
2012-09-14 23:09               ` Paul Eggleton

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=1347564379-14252-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.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