**** BEGIN LOGGING AT Mon Apr 13 02:59:57 2020
Apr 13 15:54:55 <Crofton|road> Any thgouths how I get into this situation?
Apr 13 15:55:01 <Crofton|road> NOTE: recipe linux-yocto-5.4.27+gitAUTOINC+bee554e595_ab849248b4-r0: task do_kernel_version_sanity_check: Succeeded
Apr 13 15:55:02 <Crofton|road> Bitbake still alive (5000s)
Apr 13 15:55:02 <Crofton|road> Bitbake still alive (10000s)
Apr 13 17:07:46 <khem> you did not feed enought coffee to bitbake 
Apr 13 17:16:13 <Crofton|road> I've had enough trouble with this machine without pouring coffee on it
Apr 13 20:02:38 <Crofton|road> I assume PACKAGECONFIG can be used in distro confs 
Apr 13 20:07:01 <fray> yes, that was how it was intended to be
Apr 13 20:11:56 <Crofton|road> I thought so
Apr 13 20:12:22 <Crofton|road> it cracked me up when I found a bbappend that should be handled via the existing PACKAGECONFIG
Apr 13 20:22:18 <fray> i've seen it done both ways in distro layers..
Apr 13 20:22:33 <fray> some people find it easier to manage as bbappends.. both are valid..
Apr 13 20:51:22 <kergoth> I like the distro.conf if the only change is packageconfig, just to consolidate those changes rather than scattering it across numerous files, but as you say, largely preference
Apr 13 20:51:51 <Crofton|road> the bbappend doing what is already done in a PACKAGCONFIG is annoying
**** ENDING LOGGING AT Tue Apr 14 02:59:57 2020