<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 8 March 2017 at 09:43, Peter Kjellerstedt <span dir="ltr"><<a href="mailto:peter.kjellerstedt@axis.com" target="_blank">peter.kjellerstedt@axis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id="m_-6222548947402340503:1vm" class="m_-6222548947402340503a3s m_-6222548947402340503aXjCH m_-6222548947402340503m15aad4e41ecc7842">since I see that you have integrated/staged the two patches that add<br>
inherits of pkgconfig, but not the patches that add the dummy commands,<br>
I assume you have some reservations to these patches. What are your<br>
take on the subject of blacklisting vs whitelisting the commands from<br>
the build host? I know that having these dummy commands in place helped<br>
me a great deal when updating our recipes to build correctly with RSS.</div></blockquote></div><br>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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">If the majority of people agree that this should be merged I don't have a strong opinion either way.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross<br></div></div>