On Thu, Jul 30, 2015 at 5:53 AM, Burton, Ross <ross.burton@intel.com> wrote:
On 29 July 2015 at 21:09, Christopher Larson <chris_larson@mentor.com> wrote:
The dependency on initscripts via VIRTUAL-RUNTIME_initscripts is a DEPENDS, so it's build time.  The runtime dependency is on initscripts-functions.

As far as I'm aware the sysv-generator used the rcX.d symlinks generated by update-rcd to decide what to start when, so you can't just disable the class and expect it to still work.

VIRTUAL-RUNTIME_initscripts is installed at runtime (as you can tell by its name) in packagegroup-core-boot and packagegroup-core-full-cmdline both. If I don’t want it in my images, wiping the variable is the only method that makes any sense.

So there's the problem, and breaking watchdog isn't solving it.

I don’t think taking a package that won’t even install, breaking image creation entirely, and letting it install, though not autostart, is “breaking watchdog” any worse than it already was.

That said, a better approach would probably be for update-rc.d.bbclass to explicitly DEPENDS on initscripts, not VIRTUAL-RUNTIME_initscripts. The latter isn’t guaranteed to provide initscripts-functions, it could be any recipe that provides baseline startup scripts. Adding initscripts directly would ensure that the initscripts-functions runtime dependency is satisfied in all cases.
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics