Skip to contentSkip to conversation

useradd: Handle users from a package being used in others

PATCH New Richard Purdie 1 participant 1 message Sep 5, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 useradd: Handle users from a package being used in others

From: Thomas Fitzsimmons <[email protected]>

If there is a package A (TUNE_PKGARCH) which is depended upon by B which is MACHINE_ARCH and you build B for machine X, then Y, the user isn't present in the sysroot for machine Y since the useradd code is never triggered.

The change ensures the code does get triggered and the user is present.

[YOCTO 4739]

---

meta/classes/useradd.bbclass +2 -1
index eabfc5d..a850e9d 100644
@@ -101,7 +101,7 @@ useradd_sysroot () {
 }
 
 useradd_sysroot_sstate () {
-	if [ "${BB_CURRENTTASK}" = "package_setscene" ]
+	if [ "${BB_CURRENTTASK}" = "package_setscene" -o "${BB_CURRENTTASK}" = "populate_sysroot_setscene" ]
 	then
 		useradd_sysroot
 	fi
@@ -123,6 +123,7 @@ USERADDSETSCENEDEPS_virtclass-cross = ""
 USERADDSETSCENEDEPS_class-native = ""
 USERADDSETSCENEDEPS_class-nativesdk = ""
 do_package_setscene[depends] += "${USERADDSETSCENEDEPS}"
+do_populate_sysroot_setscene[depends] += "${USERADDSETSCENEDEPS}"
 
 # Recipe parse-time sanity checks
 def update_useradd_after_parse(d):