[OE-core] sstate_clean() overzealous?

[McClintock Matthew-B29882]

On Mon, Oct 3, 2011 at 11:47 AM, Phil Blundell <philb at gnu.org> wrote:
> The sstate_clean() function in sstate.bbclass is doing (inter alia):
>
>    stfile = d.getVar("STAMP", True) + ".do_" + ss['task']
>    [...]
>    oe.path.remove(stfile + ".*")
>    oe.path.remove(stfile + "_setscene" + ".*")
>
> which means that, for tasks which set the stamp-extra-info flag to
> ${MACHINE}, it ends up blowing away the stamps for all machines rather
> than just the current one.  The net effect of this seems to be that
> there is no way to have the setscene stamps populated for more than one
> MACHINE at any time, and hence all those tasks get rerun every time you
> change MACHINE even if nothing else has been altered.
>
> Is this behaviour deliberate?  It is certainly a little bit annoying but
> I don't understand the internals of sstate well enough to judge what
> exactly that glob is trying to accomplish.

I've noticed that changing the MACHINE will also invalidate the
-native stuff as well.

-M