**** BEGIN LOGGING AT Sun Jan 24 02:59:59 2016
Jan 24 15:39:02 <yann|work> it looks like the kernel-dev manual is lacking some critical pieces of information
Jan 24 15:42:31 <yann|work> since kernel_metadata is registered before do_patch, it won't ever be run when using externalsrc, right ?
Jan 24 16:48:02 <yann|work> I have problems to convert my modified linux-sunxi recipe for orangepi-plus, to a yocto-style kernel recipe
Jan 24 16:53:11 <yann|work> linux-yocto.inc unconditionally includes linux-dts.inc, but the old-style linux-sunxi tree uses "fex" board descriptions
Jan 24 16:54:07 <yann|work> and even then, for newer device-tree-based linux-sunxi trees, the dts are hosted in the u-boot tree, so there is a problem anyway
Jan 24 17:00:56 <yann|work> well, we'll deal with  this another day, the KERNEL_DEVICETREE definition was not for this kernel anyway, obviously
Jan 24 18:36:15 <khem> yann|work: you are always welcome to send patches to improve it. Or open bugzilla tickets for improvements
Jan 24 18:36:24 <khem> since you know best where its pinching
Jan 24 18:37:15 <khem> if you send a documentation patch that is ideal and tech writers can apply it with their approvals
Jan 24 20:26:55 <obsrwr> is there a layer for including gdb with TUI functionality?
Jan 24 21:18:26 <vmeson> obsrwr: we configure with: --disable-tui -- meta/recipes-devtools/gdb/gdb-common.inc:EXTRA_OECONF = "--disable-gdbtk --disable-tui --disable-x --disable-werror \
Jan 24 21:19:05 <vmeson> you could over-ride that in a bbappend or send a patch to enable it and perhaps package it seperately.
Jan 24 21:29:21 <rZr> hi
Jan 24 21:29:42 <rZr> I am thinking about patching mesa w/ a line like :
Jan 24 21:29:55 <rZr> PROVIDES += "${@bb.utils.contains('PACKAGECONFIG', 'egl', 'virtual/wayland-egl', '', d)}"
Jan 24 21:30:03 <rZr> is it the best way to do that ?
Jan 24 21:30:32 <rZr> an additional test on WL would help too
Jan 24 22:30:09 <geotheory_> Hi. Anyone know why my update-rc.d script might be running on shutdown?  Setup with "update-rc.d boot_script.sh defaults 99"
Jan 24 22:42:27 <kergoth> why wouldn't it?
Jan 24 22:42:35 <kergoth> services generally need to start and stop
Jan 24 22:42:38 <kergoth> hence 'defaults' implies that
Jan 24 22:42:45 <kergoth> if you don't want default service behavior, then don't use those arguments
Jan 24 22:47:32 <geotheory_> kergoth, is default behaviour to run on reboot?  folder "/etc/rc6.d" contains K99boot_script.sh.  Doesn't that mean kill not start?
Jan 24 22:49:21 <kergoth> yes, it'll shut down the service when it reboots and then restart it during the normal startup process
Jan 24 22:49:26 <kergoth> last i checked, anyway
Jan 24 22:53:56 <geotheory_> kergoth, my script is running again on shutdown..
Jan 24 22:54:27 <geotheory_> i.e. it runs a script twice when I call reboot - once on powerdown and again on boot..
Jan 24 22:56:48 <geotheory_> Gotta dash but posted here https://unix.stackexchange.com/questions/257405/update-rc-d-service-running-on-shutdown
**** ENDING LOGGING AT Mon Jan 25 02:59:58 2016