just to finish off where i was going with all this INITSCRIPT_* stuff, it seems like there are a couple inaccuracies in the poky ref manual regarding those variables as listed in the glossary.
regarding INITSCRIPT_PACKAGES, yes, it's true that that variable defaults to the value of ${PN}, but this part of the explanation appears to be incorrect: "If multiple packages are specified, you need to append the package name to the other INITSCRIPT_* as an override." as i read it, it's not only if multiple packages are specified, it's also if a single package that isn't ${PN} is specified as well, correct? as in the case of meta/recipes-connectivity/openssh/openssh_6.0p1.bb: INITSCRIPT_PACKAGES = "${PN}-sshd" INITSCRIPT_NAME_${PN}-sshd = "sshd" INITSCRIPT_PARAMS_${PN}-sshd = "defaults 9" there's only one package being identified, but the fact that it isn't ${PN} requires the explicit setting of INITSCRIPT_PACKAGES, does it not? the explanation of INITSCRIPT_NAME appears to be correct -- it's a required value for each named package, so that's fine. there is an apparent error in the explanation for INITSCRIPT_PARAMS, however: "The variable is mandatory and is used in recipes when using update-rc.d.bbclass." well, it's mandatory, yes, but it's also set by default in update-rc.d.bbclass thusly: INITSCRIPT_PARAMS ?= "defaults" so there's no need for the developer to set it if that value is fine, despite what the glossary explanation suggests, correct? finally, given that default, there appear to be some superfluous lines in a few recipes, but they're not doing anyone any harm: $ grep -r "^INITSCRIPT_PARAMS = \"defaults\"" * meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb:INITSCRIPT_PARAMS = "defaults" meta/recipes-connectivity/bind/bind_9.8.1.bb:INITSCRIPT_PARAMS = "defaults" meta/recipes-bsp/apmd/apmd_3.2.2-14.bb:INITSCRIPT_PARAMS = "defaults" meta/recipes-bsp/acpid/acpid.inc:INITSCRIPT_PARAMS = "defaults" meta/recipes-extended/xinetd/xinetd_2.3.15.bb:INITSCRIPT_PARAMS = "defaults" $ does all of that make sense? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core