<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 1, 2016 at 5:35 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":10v" class="a3s aXjCH m1550bf797f8a918a">Check that 'python' is a python v2 since that is what we assume everywhere<br>
and upstream python devs recommend. We can need both python2 and python3<br>
available since we don't control the software we might download and run.<br>
<br>
Also check that python 3 is >= 3.4.0, our minimum version for <span class="il">bitbake</span>.<br>
<br>
Signed-off-by: Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>></div></blockquote></div><br>I'm curious, why don't we just have a bit of logic to figure out what the names are of the binaries, create a subdir and prepend it to the path, and add symlinks or wrapper scripts there to the real binaries on the system?<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>