**** BEGIN LOGGING AT Wed Oct 25 03:00:03 2017
Oct 25 07:41:26 <t0mmy> Hi, what is the process for requesting the backport of a patch from the master branch to the pyro branch to correct an issue?
Oct 25 07:45:04 <nrossi> t0mmy: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Backporting_fixes_to_stable_releases
Oct 25 07:48:52 <t0mmy> nrossi: thank you
Oct 25 09:14:11 <LetoThe2nd> a real classic. i tried to pick bc as an example for low hanging fruit to do a version upgrade. turns out it brings a new license, a new dependency...
Oct 25 09:14:42 <LetoThe2nd> does it actually make sense to version bump it then?
Oct 25 09:18:40 <LetoThe2nd> bluelightning: ping, concerning devtool, adding a clean command
Oct 25 09:29:58 <bluelightning> LetoThe2nd: what would clean do though? "make clean"?
Oct 25 09:30:30 <bluelightning> or bitbake -c clean?
Oct 25 09:31:02 <bluelightning> yeah I seem to recall someone else starting the bc upgrade and running into those things, I think it may have been deferred
Oct 25 09:31:34 <LetoThe2nd> bluelightningblasasdads
Oct 25 09:31:55 <LetoThe2nd> gah
Oct 25 09:32:00 <LetoThe2nd> bad wifi here sorry
Oct 25 09:32:07 <bluelightning> I've been called worse ;)
Oct 25 09:32:39 <LetoThe2nd> bluelightning: well it should do -c clean, i actually have it kinda finished here (derived from the build command, stripping out unneeded stuff)
Oct 25 09:33:06 <bluelightning> ok, sounds good
Oct 25 09:33:33 <LetoThe2nd> bluelightning: its just something i found missing in devtool in my app dev workflow
Oct 25 09:33:55 <bluelightning> LetoThe2nd: from the eSDK presumably?
Oct 25 09:34:14 <LetoThe2nd> yeah
Oct 25 09:34:55 <bluelightning> right, where you don't have access to bitbake -c clean directly... it was in the back of my mind but I hadn't really dealt with it
Oct 25 09:35:09 <LetoThe2nd> i know its actually in my specific case a shortcoming in the build system, e.g. automake not picking up c header changes in c++ apps
Oct 25 09:35:17 <LetoThe2nd> yet i think its useful
Oct 25 09:36:12 <bluelightning> yeah it is a necessary evil for some situations
Oct 25 09:36:16 <LetoThe2nd> actually i worked around it in the esdk by getting poky from the layers subdir directly.
Oct 25 09:36:47 <LetoThe2nd> but hey why not add it. so once i figure out my b0rken smtp server, patch @ you cc yocto ML?
Oct 25 09:43:11 <bluelightning> LetoThe2nd: yes please
Oct 25 09:43:46 <LetoThe2nd> bluelightning: kay
Oct 25 09:44:44 <LetoThe2nd> and i think i've sorted out the bc thing, but it means extending the ed recipe, moving to gplv3, and therefore putting the current one into meta-gplv2.
Oct 25 11:24:23 <hamis> I have a licence scanning utility which should be run on each package. I have created a class with a task to perform this scanning and recipe to fetch sources and populate sysroot so that it can be used from there inside the class. 
Oct 25 11:24:55 <hamis> Class made dependent on this recipe 
Oct 25 11:25:26 <hamis> While trying to build I am getting circular dependency error
Oct 25 11:32:23 <hamis> How can I solve such an issue.
Oct 25 11:34:08 <hamis> Is there some other way to avoid this extra recipe which is only required for pulling utility source code
**** ENDING LOGGING AT Thu Oct 26 03:00:01 2017