Re: [PATCHv3 0/5] Add dummy tools to help identify needed dependencies

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

On Wed, 2017-03-08 at 17:21 +0000, Burton, Ross wrote:
> 
> On 8 March 2017 at 09:43, Peter Kjellerstedt <peter.kjellerstedt@axis
> .com> wrote:
> > since I see that you have integrated/staged the two patches that
> > add
> > inherits of pkgconfig, but not the patches that add the dummy
> > commands,
> > I assume you have some reservations to these patches. What are your
> > take on the subject of blacklisting vs whitelisting the commands
> > from
> > the build host? I know that having these dummy commands in place
> > helped
> > me a great deal when updating our recipes to build correctly with
> > RSS.
> > 
> FWIW I wasn't entirely keen on how the blacklisting had to be very
> careful about how PATH was manipulated, which is why I merged to my
> staging branch the fixes but not the dummy commands.
> 
> If the majority of people agree that this should be merged I don't
> have a strong opinion either way.

Ultimately I think there is a better solution than this but I haven't
had time to look at that as yet.

I do worry that it makes assumptions about PATH that may or may not be
valid everywhere, equally I do see it could be useful.

So I also have mixed feelings...

Cheers,

Richard