Re: [OE-core] [PATCH] sanity.bbclass: verify that user isn't building in PSEUDO_IGNORE_PATHS

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

Hi,

On Wed, 2021-01-27 at 17:46 +0800, ChenQi wrote:
>  Is it possible to use an opposite way for pseudo path filtering?
>  Instead of ignoring paths, only take into consideration paths in
> something like PSEUDO_CONSIDER_PATHS.
>  The list should be short. ${D}, ${PKGD}, ${PKGDEST},
> ${IMAGE_ROOTFS}?

Its a good question, I was convinced by the pseudo authors that it was
a bad idea. The reason being that it isn't just the above paths but we
also need to catch calls where files are transiently in other
directories or in other parts of the filesystem such as /tmp/. Code
creates files in interesting and convoluted ways to preserve
permissions, for security reasons and so on and there was a worry that
masking just a specific list would cause a different set of problems.
It probably shouldn't be crossing filesystem boundaries doing it but I
know there were complications due to it.

That said, now that pseudo can support path filtering, it may be worth
an experiment to see how whether it could work better than what we're
doing now. The algorithm (whether its include or exclude) should be
relatively easy to test.

I can also say the above list would need expanding as some sstate
objects need to preserve ownership/permissions during creating and so
on. It probably would still be simpler than our current ignore list
though.

Cheers,

Richard