**** BEGIN LOGGING AT Thu Sep 12 02:59:59 2013
Sep 12 09:21:41 <ant_work> bluelightning: hi
Sep 12 09:24:06 <bluelightning> hi ant_work
Sep 12 09:31:23 <ant_work> I've discovered a strange issue
Sep 12 09:31:26 <ant_work> http://cgit.openembedded.org/meta-openembedded/tree/meta-initramfs/recipes-bsp/kexecboot/kexecboot-cfg_0.1.bb#n51
Sep 12 09:31:44 <ant_work> on collie it happened that the same text was echoed twice
Sep 12 09:32:09 <ant_work> I'mbuilding w/out rm_work
Sep 12 09:32:24 <ant_work> so, the first fix is s/>>/>/
Sep 12 09:32:52 <ant_work> but I'm wondering about how it can happen that the boot.cfg is still present on secund build
Sep 12 09:34:25 <ant_work> btw I've the 3.10 to commit
Sep 12 09:35:55 <ant_work> bluelightning: I've digged a bit and found that the sstate mtime was invalid so kexecboot_cfg would have been rebuilt
Sep 12 09:37:03 <bluelightning> well if do_install was re-executed (because one of its inputs changed) I can see how that would cause problems
Sep 12 09:37:29 <bluelightning> this should be rewritten so that the stuff in the prepend changes the file in ${D} not the file in ${S}
Sep 12 09:37:57 <bluelightning> (and of course do it in do_install and not in do_install_prepend)
Sep 12 09:38:55 <ant_work> ah
Sep 12 09:39:17 <ant_work> tbh I don't remember why I left append >> and not straight >
Sep 12 09:39:54 <bluelightning> yes, that is odd... at first I thought it was appending to a static file but then I noticed nothing in SRC_URI
Sep 12 09:40:04 <ant_work> so changin the file in S is the culprit
Sep 12 09:40:41 <bluelightning> yes, that should avoid re-execution issues
Sep 12 09:42:35 <ant_work> hmm.. maybe at the very beginning we tried to embed the image name in the file, so pre-crating part of boot.cfg and adding the rest later
Sep 12 09:43:46 <ant_work> there is no way to know the image so this is littl epoint
**** ENDING LOGGING AT Fri Sep 13 02:59:58 2013