All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Ho" <Michael.Ho@bmw.de>
To: <openembedded-core@lists.openembedded.org>
Cc: Michael Ho <Michael.Ho@bmw.de>
Subject: [PATCH 2/5] package_ipk.bbclass: add PACKAGE_ADD_METADATA_IPK to sstate variables
Date: Mon, 25 May 2020 09:43:38 +0200	[thread overview]
Message-ID: <1590392621-327991-2-git-send-email-michael.ho@bmw.de> (raw)
In-Reply-To: <1590392621-327991-1-git-send-email-michael.ho@bmw.de>

From: Michael Ho <Michael.Ho@bmw.de>

Add PACKAGE_ADD_METADATA_IPK to IPKEXTRAVARS so it affects the sstate hash
of do_package_write_ipk.

Signed-off-by: Michael Ho <Michael.Ho@bmw.de>
---
 meta/classes/package_ipk.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/package_ipk.bbclass b/meta/classes/package_ipk.bbclass
index c008559..79cb36c 100644
--- a/meta/classes/package_ipk.bbclass
+++ b/meta/classes/package_ipk.bbclass
@@ -238,7 +238,7 @@ def ipk_write_pkg(pkg, d):
         bb.utils.unlockfile(lf)
 
 # Have to list any variables referenced as X_<pkg> that aren't in pkgdata here
-IPKEXTRAVARS = "PRIORITY MAINTAINER PACKAGE_ARCH HOMEPAGE"
+IPKEXTRAVARS = "PRIORITY MAINTAINER PACKAGE_ARCH HOMEPAGE PACKAGE_ADD_METADATA_IPK"
 ipk_write_pkg[vardeps] += "${@gen_packagevar(d, 'IPKEXTRAVARS')}"
 
 # Otherwise allarch packages may change depending on override configuration
-- 
2.7.4


  reply	other threads:[~2020-05-25  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  7:43 [PATCH 1/5] package.bbclass: add PACKAGE_ADD_METADATA to sstate variables Michael Ho
2020-05-25  7:43 ` Michael Ho [this message]
2020-05-25  7:43 ` [PATCH 3/5] package_deb.bbclass: add PACKAGE_ADD_METADATA_DEB " Michael Ho
2020-05-25  7:43 ` [PATCH 4/5] package_rpm.bbclass: add PACKAGE_ADD_METADATA_RPM " Michael Ho
2020-05-25  7:43 ` [PATCH 5/5] ref-manual: add PACKAGE_ADD_METADATA documentation Michael Ho
2020-05-25  8:02 ` ✗ patchtest: failure for "package.bbclass: add PACKAGE_A..." and 4 more Patchwork

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=1590392621-327991-2-git-send-email-michael.ho@bmw.de \
    --to=michael.ho@bmw.de \
    --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 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.