**** BEGIN LOGGING AT Wed Sep 11 03:00:21 2019
Sep 11 08:03:30 <Foxdie> Good morning
Sep 11 08:12:40 <Foxdie> Relating to yesterdays conversation about compiling npm packages, I believe I've found the reason why `inherit npm` and then `oe_runnpm` was hanging; "npm ERR! Registry not defined and registry files not found"
Sep 11 08:16:21 <Foxdie> Fix for that appears to have been simply adding `NPM_REGISTRY = "https://registry.npmjs.org/"` (without backticks) before the do_install() block :)  
Sep 11 08:16:38 <Foxdie> Running another build now to see if there are any other errors natively using npm.bbclass rather than a sub-function 
Sep 11 10:02:55 <Foxdie> Morning rburton
Sep 11 10:03:47 <Foxdie> I followed your advice and tried using `inherit npm` in debug mode, it turns out there's no default value to `NPM_REGISTRY` in that scenario 
Sep 11 10:12:19 * rburton shrugs
Sep 11 10:12:21 <rburton> never used it, sorry
Sep 11 10:12:46 <rburton> so i've no idea why you need to use that
Sep 11 10:12:58 <rburton> the npm class in oe-core *should* basically do everything for you
Sep 11 10:14:28 <rburton> like https://github.com/intel-iot-devkit/meta-iot-cloud/blob/master/recipes-oisp/oisp-cli/oisp-cli_1.1.0.bb
Sep 11 10:15:28 <rburton> https://github.com/intel/iot-web-layers/blob/master/meta-iot-web/recipes-devtools/galileo-io/galileo-io_0.9.4.bb is even leaner
Sep 11 10:15:49 <rburton> not sure why that sets LICENSE_PN* to the same as LICENSE, that's redundant
Sep 11 10:17:57 <Foxdie> I'm not sure why it's not working for me then. I am however making an updated bitbake recipe to factor it in, testing it now
Sep 11 10:19:06 <rburton> my subtext is why do you need to set NPM_REGISTRY as the other recipes don't
Sep 11 10:19:44 <Foxdie> Setting NPM_REGISTRY doesn't work either :/
Sep 11 10:20:36 <rburton> npm.bbclass *does not use that variable* so what does?
Sep 11 10:20:36 <Foxdie> I'm honestly unsure bud, this is weird, the recipe isn't particularly complex, the only thing I'm doing is running `npm install` relying on an external package.json which just lists deps.
Sep 11 10:20:50 <Foxdie> I don't know if imyller (author) intended for it to be used this way.
Sep 11 10:24:16 <Foxdie> Hmm this appears interesting;
Sep 11 10:24:20 <Foxdie> ERR! argv "~/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/npm-packages/1.0.0-r1/recipe-sysroot-native/usr/bin/node" "~/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/npm-packages/1.0.0-r1/recipe-sysroot-native/usr/bin/npm" "--arch=arm" "--target_arch=arm" "--production" "--no-registry" "install"
Sep 11 10:24:58 <Foxdie> Using `oe_runnpm install` is _intentionally_ disabling use of any registry, hence the failure.
Sep 11 10:25:19 <Foxdie> Bugger it. Back to `inherit npm-install` I go :)  
Sep 11 10:26:35 <Foxdie> Thanks anyway rburton, I appreciate the effort ;)  
Sep 11 11:12:25 <Foxdie> Okay, little bit more testing and cleanup, this is what I've settled on for the IRC log viewers; https://pastebin.com/Ch8VbAK2
Sep 11 11:15:23 <rburton> use install not cp
Sep 11 11:16:37 <Foxdie> Will install work recursively? 
Sep 11 11:16:47 <Foxdie> (there's about 10k files in that folder tree)
Sep 11 14:19:09 <laplante> RP: (or whomever) could you please clarify why do_populate_sdk is in SSTATETASKS, but doesn't have a _setscene variant? Is it because do_populate_sdk only utilizes sstate for its manifest generation?
**** ENDING LOGGING AT Thu Sep 12 03:02:41 2019