**** BEGIN LOGGING AT Mon Mar 06 03:00:00 2017
Mar 06 17:24:43 <fischerm> khem: so it does only happen if you turn on PACKAGECONFIG[python]
Mar 06 17:24:53 <fischerm> khem: the problem is boost build system is high on glue
Mar 06 17:25:22 <fischerm> khem: they don't have a config option to --without-numpy or whatever, so with 1.63 if you turn on python it will build in numpy
Mar 06 17:25:37 <fischerm> khem: I suspect whoever updated the recipe didn't build with python
Mar 06 18:05:04 <Crofton|work> lib/perl5: Cannot create symlink to 'perl': File exists
Mar 06 18:05:05 <Crofton|work> tar: ./usr/lib/perl5: Cannot create symlink to 'perl': File exists
Mar 06 18:05:05 <Crofton|work> tar: ./usr/lib/perl5: Cannot create symlink to 'perl': File exists
Mar 06 18:05:05 <Crofton|work> tar: Exiting with failure status due to previous errors
Mar 06 18:05:20 <Crofton|work> trying to build jethro on Fedora 23. Any ideas why I see this?
Mar 06 18:05:41 <darknighte> hey folks, when using a PACKAGECONFIG_append in a .bb/.bbappend, is it still correct/considered better to add a _pn-<PKGNAME> ?
Mar 06 18:12:08 <Crofton|work> one step forward, half a step back
Mar 06 18:14:11 <darknighte> k, for those that might be wondering, while it is useful in the local.conf, it is not required and considered redundant in a .bbappend, in most cases.
Mar 06 18:59:14 <khem> fischerm: yes thats what I thought and hinted to Phil other day 
Mar 06 19:01:08 <khem> darknighte: it really depends on your dev model, doing it in recipes or config namespace you can achieve same effect, I personally consider bbappend approach a bit better since I can discretely see where stuff is being added removed layerwise 
Mar 06 19:34:01 <kergoth> i like setting packageconfigs in the distro .conf rather than via append, so the distro configuration isn't quite so spread out
Mar 06 19:34:02 * kergoth yawns
Mar 06 19:49:19 <fischerm> Crofton|work: any success with nuking sstate?
**** ENDING LOGGING AT Tue Mar 07 03:00:02 2017