<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 30, 2015 at 5:53 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div class="gmail_quote">On 29 July 2015 at 21:09, Christopher Larson <span dir="ltr"><<a href="mailto:chris_larson@mentor.com" target="_blank">chris_larson@mentor.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>The dependency on initscripts via VIRTUAL-RUNTIME_initscripts is a DEPENDS, so it's build time. The runtime dependency is on initscripts-functions.</div><div><br></div><div>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.</div><span><font color="#888888"><div></div></font></span></div></blockquote></div><br></span>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.</blockquote></div><br></span>So there's the problem, and breaking <span class="il">watchdog</span> isn't solving it.</blockquote></div><br>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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.<br>-- <br><div class="gmail_signature"><div dir="ltr">Christopher Larson<br>kergoth at gmail dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div></div>
</div></div>