[OE-core] wpa-supplicant strangeness after pull

[Steve Sakoman]

On Wed, Feb 29, 2012 at 3:56 PM, Khem Raj <raj.khem at gmail.com> wrote:

> and this is yet another case where basichash exposes an underlying problem
>
> see the sed command in below snippet
>
> install -m 644 ${S}/dbus/dbus-wpa_supplicant.conf
> ${D}/${sysconfdir}/dbus-1/system.d
> install -d ${D}/${datadir}/dbus-1/system-services
> sed -i -e s:${base_sbindir}:${sbindir}:g ${S}/dbus/*.service
> install -m 644 ${S}/dbus/*.service ${D}/${datadir}/dbus-1/system-services
>
> that command can only be run correctly once unless you delete ${S}
> since its sedding something in ${S}
> and we know base_sbindir (/sbin) and sbindir(/usr/sbin) are close
> enough expressionwise

Makes perfect sense.  But quite scary -- makes me wonder how many more
things like this are lurking as yet undetected!  This caused an
obvious problem right at boot time so it was easy to detect.

>> I'm beginning to suspect I ought to just do a clean build after every
>> pull in order to remain productive!
>
> That will hide these kind of issues you bring forward :)

You are right of course.  Sadly I only get to bill for getting client
work done, not for debugging the build system :-(

So my motivation is typically to just get things working again
quickly, rather than to dig in and find the root cause.  Need to find
a happy balance.  Lately I've been spending the time to document the
issue on the list, but if a clean rebuild fixes things I just forge on
with client work.

Steve