**** BEGIN LOGGING AT Tue Apr 09 03:00:03 2019 Apr 09 14:37:41 a bbappend here appends to DEPENDS and EXTRA_OECONF. however, I want to make sure this is done only for the target version of the package, not the native one. Apr 09 14:37:45 how can I do that? Apr 09 14:48:46 dv_: DEPENDS_append_class-target = " ..." Apr 09 14:55:28 thx Apr 09 18:05:05 is this an appropriate place to ask questions about bitbake? Apr 09 18:05:26 yes Apr 09 18:05:27 sure Apr 09 18:07:17 so, i'm trying to build something with bitbake on NixOS, and NixOS is a bit quirky in that it doesn't have a /bin/bash Apr 09 18:07:36 everything seems to be looking for that, so I was wondering how I can provide an explicit path for bash Apr 09 18:07:44 ideally in some sort of global way across everything bitbake is building Apr 09 18:08:00 our recipes just run the underlying tools Apr 09 18:08:02 make, autoconf, etc Apr 09 18:08:16 i doubt we have the level of control you want to change how the underlying buildsystems are looking for bash if and when they want it Apr 09 18:08:25 for ourselves, we use /bin/sh, not /bin/bash Apr 09 18:08:30 so it's only the underlying buildsystems that might require it Apr 09 18:08:30 got it; so environment should pass through? Apr 09 18:08:37 yup, nixos has that :) Apr 09 18:08:42 environment *variables* are filtered, but other than that, yes Apr 09 18:09:25 ah, so if i wanted to some environment variables to not be filtered, or to be explicitly provided, is that possible? Apr 09 18:09:34 (or maybe that's the wrong approach generally?) Apr 09 18:10:07 you can, yes, by setting BB_ENV_EXTRAWHITE in the shell environment, after sourcing the setup scripts (as they set it) Apr 09 18:10:12 s/setting/appending to/ Apr 09 18:10:21 i.e. BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MY_EXTRA_VARIABLE" Apr 09 18:10:32 this will let MY_EXTRA_VARIABLE into bitbake's metadata Apr 09 18:10:55 it won't re-export it into the buildsystems we call unless you explicitly use 'export' in local.conf or similar, but that would make it available for use inside EXTRA_OEMAKE Apr 09 18:11:21 that said, if you're just trying to muck with SHELL, i wouldn't advise it Apr 09 18:12:48 hm, yeah, that makes sense Apr 09 18:15:27 would there be a better way to set the shell? Apr 09 18:15:43 or maybe to prepend to the path that the packages see? Apr 09 18:16:04 i'm not sure how autoconf/etc. actually go about trying to find bash **** ENDING LOGGING AT Wed Apr 10 02:59:57 2019