From: Adam Blank <adam.blank.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Adam Blank <adam.blank.g@gmail.com>
Subject: [PATCH 4/4] package: update the comment block explaining 'emit_pkgdata'
Date: Thu, 02 Apr 2026 16:55:01 +0200 [thread overview]
Message-ID: <20260402-dead_code_and_unification-v1-4-5a3906b6340d@gmail.com> (raw)
In-Reply-To: <20260402-dead_code_and_unification-v1-0-5a3906b6340d@gmail.com>
Signed-off-by: Adam Blank <adam.blank.g@gmail.com>
---
meta/classes-global/package.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/classes-global/package.bbclass b/meta/classes-global/package.bbclass
index bd32a6ede5..fc3c539f68 100644
--- a/meta/classes-global/package.bbclass
+++ b/meta/classes-global/package.bbclass
@@ -41,7 +41,7 @@
#
# k) package_depchains - Adds automatic dependencies to -dbg and -dev packages
#
-# l) emit_pkgdata - saves the packaging data into PKGDATA_DIR for use in later
+# l) emit_pkgdata - saves the packaging data into PKGDESTWORK for use in later
# packaging steps
inherit packagedata
@@ -610,4 +610,3 @@ python do_packagedata_setscene () {
sstate_setscene(d)
}
addtask do_packagedata_setscene
-
--
2.43.0
next prev parent reply other threads:[~2026-04-02 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 14:54 [PATCH 0/4] Slight code cleanup - remove dead code, fix typos, unify patterns Adam Blank
2026-04-02 14:54 ` [PATCH 1/4] lib/packagedata.py: slight improvement to code readability Adam Blank
2026-04-02 14:54 ` [PATCH 2/4] package_pkgdata: fix typo to stop calling undefined function Adam Blank
2026-04-02 15:00 ` Patchtest results for " patchtest
2026-04-02 14:55 ` [PATCH 3/4] sstate: remove dead code and unify path operations Adam Blank
2026-04-02 14:55 ` Adam Blank [this message]
2026-04-02 15:00 ` Patchtest results for [PATCH 4/4] package: update the comment block explaining 'emit_pkgdata' patchtest
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=20260402-dead_code_and_unification-v1-4-5a3906b6340d@gmail.com \
--to=adam.blank.g@gmail.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