From: Vincent Davis Jr <vince@underview.tech>
To: openembedded-core@lists.openembedded.org
Cc: Vincent Davis Jr <vince@underview.tech>
Subject: [PATCH 09/19] nfs-utils: rename kernel prefix
Date: Sat, 11 Jul 2026 01:23:53 -0400 [thread overview]
Message-ID: <20260711052403.1292286-9-vince@underview.tech> (raw)
In-Reply-To: <20260711052403.1292286-1-vince@underview.tech>
Utilize preset variable KERNEL_PACKAGE_NAME
to ensure uninformative with builds if
KERNEL_PACKAGE_NAME variable were to change.
Signed-off-by: Vincent Davis Jr <vince@underview.tech>
---
meta/recipes-connectivity/nfs-utils/nfs-utils_2.9.1.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.9.1.bb b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.9.1.bb
index 6f00bee0d8..5aa6ff01cc 100644
--- a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.9.1.bb
+++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.9.1.bb
@@ -10,9 +10,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=95f3a93a5c3c7888de623b46ea085a84"
# util-linux for libblkid
DEPENDS = "libcap libevent util-linux sqlite3 libtirpc libxml2 libnl"
RDEPENDS:${PN} = "netbase ${PN}-client"
-RRECOMMENDS:${PN} = "kernel-module-nfsd"
+RRECOMMENDS:${PN} = "${KERNEL_PACKAGE_NAME}-module-nfsd"
-inherit useradd
+inherit useradd kernel-vars
USERADD_PACKAGES = "${PN}-client"
USERADD_PARAM:${PN}-client = "--system --home-dir /var/lib/nfs \
@@ -28,7 +28,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/nfs-utils/${PV}/nfs-utils-${PV}.tar.x
SRC_URI[sha256sum] = "302846343bf509f8f884c23bdbd0fe853b7f7cbb6572060a9082279d13b21a2c"
-# Only kernel-module-nfsd is required here (but can be built-in) - the nfsd module will
+# Only ${KERNEL_PACKAGE_NAME}-module-nfsd is required here (but can be built-in) - the nfsd module will
# pull in the remainder of the dependencies.
INITSCRIPT_PACKAGES = "${PN} ${PN}-client"
--
2.43.0
next prev parent reply other threads:[~2026-07-11 5:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 5:23 [PATCH 01/19] kernal-vars: introduce new class Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 02/19] kernel: introduce kernel-vars class Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 03/19] packagegroup-self-hosted: rename kernel prefix Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 04/19] packegroup-core-boot: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 05/19] packagegroup-base: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 06/19] ofono: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 07/19] iptables: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 08/19] watchdog: " Vincent Davis Jr
2026-07-11 5:23 ` Vincent Davis Jr [this message]
2026-07-11 5:23 ` [PATCH 10/19] mdadm: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 11/19] systemd: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 12/19] util-linux: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 13/19] connman: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 14/19] hwlatdetect: " Vincent Davis Jr
2026-07-11 5:23 ` [PATCH 15/19] v86d: " Vincent Davis Jr
2026-07-11 5:24 ` [PATCH 16/19] efivar: " Vincent Davis Jr
2026-07-11 5:24 ` [PATCH 17/19] parted: " Vincent Davis Jr
2026-07-11 5:24 ` [PATCH 18/19] ltp: " Vincent Davis Jr
2026-07-11 5:24 ` [PATCH 19/19] libnl: " Vincent Davis Jr
2026-07-11 20:22 ` [OE-core] [PATCH 01/19] kernal-vars: introduce new class Richard Purdie
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=20260711052403.1292286-9-vince@underview.tech \
--to=vince@underview.tech \
--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