From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH 2/2] ref-manual/variables.rst: document the PACKAGEFUNCS variable
Date: Tue, 18 Aug 2026 11:20:29 +0200 [thread overview]
Message-ID: <20260818-packagefuncs-v1-2-1f26764cbdd3@bootlin.com> (raw)
In-Reply-To: <20260818-packagefuncs-v1-0-1f26764cbdd3@bootlin.com>
Added by commit 4b46c1f6e891 ("Initial population") in OE-Core. This
completes the variables used during do_package, as
PACKAGE_PREPROCESS_FUNCS and PACKAGESPLITFUNCS are already documented.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/ref-manual/variables.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 09136803c..724293a58 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7360,6 +7360,12 @@ system and gives an overview of their function and contents.
:ref:`ref-tasks-configure` task, then you need to use
:term:`PACKAGECONFIG_CONFARGS` appropriately.
+ :term:`PACKAGEFUNCS`
+ The :term:`PACKAGEFUNCS` variable holds a list of functions which are
+ executed to process metadata based on split packages found in the
+ :term:`PKGDEST` directory. These functions are executed in the
+ :ref:`ref-classes-package` class in the order found in the list.
+
:term:`PACKAGEGROUP_DISABLE_COMPLEMENTARY`
For recipes inheriting the :ref:`ref-classes-packagegroup` class, setting
:term:`PACKAGEGROUP_DISABLE_COMPLEMENTARY` to "1" specifies that the
--
2.55.0
prev parent reply other threads:[~2026-08-18 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 9:20 [PATCH 0/2] Document package related variables Antonin Godard
2026-08-18 9:20 ` [PATCH 1/2] ref-manual/variables.rst: document the PACKAGE_NO_LOCALE variable Antonin Godard
2026-08-18 9:20 ` Antonin Godard [this message]
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=20260818-packagefuncs-v1-2-1f26764cbdd3@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.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 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.