**** BEGIN LOGGING AT Sun Dec 28 02:59:59 2014 Dec 28 19:54:44 * b1tninja prods RP gently Dec 28 19:57:36 RP, is blowing up capacitors Dec 28 20:00:27 lol fun Dec 28 20:05:01 http://media.ccc.de/browse/congress/2014/31c3_-_6240_-_en_-_saal_g_-_201412271400_-_reproducible_builds_-_mike_perry_-_seth_schoen_-_hans_steiner.html#video Dec 28 20:10:56 * b1tninja begins looking into how to submit a patch to Yocto Dec 28 20:12:04 you read the oe-core list? Dec 28 20:13:06 the website links to https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide gonna follow that link... oe-core list? no i haven't mailing list? Dec 28 20:13:27 see the list archives to see what submissions look like Dec 28 20:14:18 alright thanks Dec 28 20:15:38 i was trying to hunt down RP becuase he committed a patch for the particular issue i was having, but a recipe the wpa-supplicant and hostap packages needed a tweak on the do_configure for it to build on my system Dec 28 20:16:10 so hes like the resident expert =p Dec 28 20:17:14 well, ask here or on the list. More than one person might have an ida Dec 28 20:29:00 this is basically what i had to do to prevent my own host-os, system libraries from poisoning the build of wpa-supplicant for my poky image, http://pastebin.com/e1EcC1TV Dec 28 20:30:43 and i think its needed because of: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=29ec481c46b6f10e31a7bcaa84f6d77f280be6ec Dec 28 20:31:57 looks reasonable to me Dec 28 20:32:42 Can you make a proper commit with good commit message and send to the oe-core list? Dec 28 20:33:12 i will try to run through the steps Dec 28 20:33:19 thanks Dec 28 21:10:17 whats the best practice, im thinking it might be beneficial to some to checkout the build at that commit i refrenced, and do the change there? then it can be merged ? Dec 28 21:10:30 then that way older-build users could have easier access to it? Dec 28 21:10:34 no, commits sent upstream must be based on master Dec 28 21:10:38 k Dec 28 21:11:09 the job of adapting your change to the current state of the repository, if necessary, is on the contributor, not the maintainer, in open source projects, generally Dec 28 21:11:28 ah ok im newb to the whole process Dec 28 22:33:42 b1tninja: I wouldn't say expert on that issue, your change looks reasonable to me fwiw though Dec 28 22:35:50 alright, cool. I did verify the build worked with the changes (including wpa)... and looked to see how the .config got included, my one concern was i didn't understand the use of the EXTRA_CFLAGS variable, but it might've not been needed for the drivers makefile Dec 28 22:54:03 when i attempt to submit this, im not suppose to write Sign-off-by: correct? Thats for the maintainers? Dec 28 22:56:41 you should have yours Dec 28 22:56:41 oh nevermind Dec 28 22:56:45 yea i see Dec 28 22:56:57 its to prove authorship for licensing reasons Dec 28 22:57:22 and so we know who to beat if it causes troble :) Dec 28 22:57:28 =p Dec 28 23:01:42 Crofton|work, nice link about the reproducible builds Dec 28 23:01:49 thanks Dec 28 23:02:00 I was surfing 31c3 talks this afternoon Dec 28 23:20:38 im confused now, i thought i was submitting a patch to yocto, looks like im suppose to send it to oe-core... *checks out oe-core repo* Dec 28 23:20:46 or can i submit against poky Dec 28 23:41:06 Crofton|work, i think i've done it... thanks for your encouragement Dec 28 23:41:07 lol Dec 28 23:49:04 http://thread.gmane.org/gmane.comp.handhelds.openembedded.core woot Dec 28 23:49:46 and would've never figured it out without your commit RP, so thank you too Dec 29 00:00:07 the poky repository is an integration of components, including oe-core and meta-yocto (which provides the poky distro, despite the wrong layer name) Dec 29 00:04:58 ah ok i was wondering, cuz i started originally frmo the edison-src tarball and it had its own meta layer Dec 29 00:07:42 the meta and scripts dirs in the poky dir are oe-core. Dec 29 00:07:48 poky/meta is from oe-core/meta **** ENDING LOGGING AT Mon Dec 29 02:59:58 2014