| 00:08.06 | *** join/#oe miraage (~miraage@S01060050baab2c59.vc.shawcable.net) |
| 00:21.17 | jacques | hmm there's a lot more going on with patching than I thought - apparently patcher changes the patch - or rather creates a new patch |
| 00:21.30 | jacques | and calls it .txt in the .patches dir |
| 00:22.23 | treke | patcher does more than just patch |
| 00:22.37 | treke | it also keeps track of enough to be able to regenerate the patch later. |
| 00:23.14 | jacques | I tried creating my patch with diff -urN but it still does not apply and I cant get debugging info from patcher |
| 00:23.34 | mikelp | correct patch level ? |
| 00:24.58 | jacques | I've tried a couple of different ones - what's it supposed to be? |
| 00:24.58 | *** join/#oe kergoth (~kergoth@proxyle01.ext.ti.com) |
| 00:26.45 | mikelp | depends where you are when you call diff ;) |
| 00:27.08 | pb_ | treke: I've always found patcher to be more trouble than it's worth, really. |
| 00:27.31 | pb_ | I've often been tempted to write a new base_do_patch that just calls patch directly. |
| 00:29.02 | treke | I found it helpful when having to fight with build systems, but that doesnt happen as much in oe as it did in buildroot. |
| 00:29.21 | jacques | hmm I think I just made a patch that applied |
| 00:31.09 | jacques | my level was wrong |
| 00:31.21 | jacques | i thought I had tried that but I guess my testing method was flawed |
| 00:31.39 | jacques | I was trying to anticipate whether a patch would apply correctly by using patch |
| 00:31.53 | treke | eh? |
| 00:31.58 | treke | nothing wrong with that |
| 00:32.11 | mikelp | --dry-run is a wonderful thing |
| 00:32.29 | treke | mikelp: hows the kernel debugging going? |
| 00:32.29 | *** join/#oe sunny (sunny@sunny.cloaked) |
| 00:32.54 | jacques | yeah I use --dry-run all the time |
| 00:32.56 | mikelp | treke: not at the moment, I'm IM'ing someone I haven't spoken to in months |
| 00:32.56 | *** join/#oe sunny (sunny@sunny.cloaked) |
| 00:33.47 | jacques | cool it completed |
| 00:35.27 | jacques | now to run the whole build from the beginning |