sstate-cache contains many seemingly useless siginfo files

[Mike Crowe <mac@mcrowe.com>]

Our sstate-cache cleanup script was written long before
80b3974081c4a8c604e23982a6db8fb32c616058, so it only pruned siginfo files
if the corresponding tgz file had not been accessed recently.

This worked well until siginfo files started being written for every task -
even those that didn't also generate a tgz file such as unpack, configure
and compile.

I've just cleared up over two million siginfo files from our sstate-cache!

This exercise has left me wondering why these siginfo files are being
written to the sstate-cache in the first place.
80b3974081c4a8c604e23982a6db8fb32c616058 suggests that they aren't being
used by anyone.

If writing the files is necessary, is there any reason not to just delete
these files periodically or could that confuse a build that is in progress?

Thanks.

Mike.