<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 28 March 2017 at 13:18, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3ms" class="a3s aXjCH m15b14db286875907"> ok, i thought i knew what you meant but now, i'm just drawing a<br>
blank. in what way is that not testing for a non-empty string as the<br>
value of D? what painfully obvious clue am i missing?</div></blockquote></div><br>The gconf_postinst is shell to be executed in the package management postinst code, so either at rootfs time, or first boot for the ones that didn't work at rootfs, or when the package is installed on the target.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The postinst can tell those apart by inspecting the value of the environment variable $D, which if set means the postinst is running on the host in the rootfs context, so should prefix all paths with $D.</div><div class="gmail_extra"><br></div><div class="gmail_extra">$D *needs* to be fetched from the environment when the script is executing, and using ${D} will result in *bitbake* expanding it whilst writing the package, where it is the path to the package staging directory.</div><div class="gmail_extra"><br></div><div class="gmail_extra">(yes, using a different variable name that wasn't overloaded wouldn't cause this problem)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>