**** BEGIN LOGGING AT Sat Sep 25 02:59:56 2021
Sep 25 10:40:20 <mort> rburton: the situation is: I have made a depot_tools package for Google's depot tools, another recipe uses the depot_tools recipe to download/configure/build
Sep 25 10:40:46 <mort> Google's depot_tools is a collection of scripts you're supposed to point your $PATH to
Sep 25 10:41:23 <mort> I can't just dump all of depot_tools into ${D}/usr/bin because it would conflict with other things, for example depot_tools contains ninja which is also provided by another package which makes bitbake angry
Sep 25 10:42:11 <mort> ideally, I would want the depot_tools package itself to say that anything which uses depot_tools should have <native sysroot>/usr/bin/depot_tools in its $PATH
Sep 25 10:42:23 <mort> ideally that would also work in the SDK
Sep 25 17:38:25 <rburton> mort: depot-tools recipe should install to bindir/depot-tools, then write a class that depends on depot-tools-native and sets EXTRANATIVEPATH=depot-tools
Sep 25 17:39:09 <mort> rburton: ah, I see. So EXTRANATIVEPATH is like a $PATH variable but relative to bindir?
Sep 25 18:53:27 <mort> there might be something I'm not understanding. When I depend on the python-native package, there's no recipe-sysroot-native/${bindir}/python binary, instead there's a recipe-sysroot-native/${bindir}/python-native folder which contains the python binary
Sep 25 18:53:43 <mort> are you supposed to have to use EXTRANATIVEPATH="python-native" to use python?
Sep 25 19:25:58 <khem> mort: usually you would `inherit python3native`
Sep 25 19:49:14 <mort> I see
Sep 25 19:49:41 <mort> python2native in my case tho because :(
Sep 25 22:06:28 <rburton> Yes, that.
**** ENDING LOGGING AT Sun Sep 26 02:59:58 2021