**** BEGIN LOGGING AT Sun May 18 02:59:59 2014 May 18 09:55:38 Are _prepend()/_append() bash functions executed in subshells, or is the text just inserted into one single script of statements to be executed ? May 18 10:01:09 its appended to the script May 18 10:01:19 you can see the scripts in the tmp/ directory May 18 10:05:17 XorA, aha. thanks May 18 10:06:26 so are the run.do_* executed in the same shell ? the reason I ask is that I had do "cd ${S}; do_stuff(); cd ${B}" in a configure_prepend May 18 10:06:43 If I left out the final "cd ${B}", do_compile() fails May 18 10:07:56 I thought it "task" ran in its own shell May 18 10:08:09 but _prepend_append to a task runs in the same shell May 18 10:09:15 oh May 18 10:09:31 of course, i screw things up if i dont cd {B}.. May 18 10:30:40 kroon: wrap your cd ; do_stuff in () May 18 10:30:41 e.g. May 18 10:30:50 ( cd ${S} ; do do_stuff ) May 18 10:31:02 that will return to the original directory May 18 10:31:25 koen, yeah good point May 18 10:32:08 I try to do that for every action involving 'cd' nowadays May 18 10:32:34 OE classes change too much to hope it will work otherwise May 18 10:42:27 I'm doing B!=S fixes for packages in meta-oe that I have never heard of. I don't know how to test these changes, anymore that making sure they build. May 18 10:42:58 Is it be ok to send patches anyway, or is it expected that developers do more testing than the above mentioned ? May 18 10:44:44 I guess I could build with autotools-brokensep, then a build with autools and fixes, and see what changed May 18 11:01:32 if it builds it's OK for S!=B May 18 11:15:30 ok May 18 13:56:50 * kroon wants latest xbmc on his rpi **** ENDING LOGGING AT Mon May 19 02:59:58 2014