Compile Kernel on RPI2 from RBP2-sources-osmc

[sam_nazarko]

@SethCohn

What’s the advantage to making the standard be a diff against nothing, versus having a real “.config” file you just put into place? You’re already running a script, right? So rather than a patch file diff, you’d only have to maintain a single plain config, and changes would be much easier to track (and generate…) Otherwise, changes requiring making a patch TO a patch file, which is awkward.

It’s not as complex as you’ve made it seem. Restoring the original config and generating a config based diff can be done with an individual command.

• patch -p1 < atv-000*.patch to create config
• diff -u /dev/null .config > atv-000*.patch to create the patch containing the config.

The build system is patch oriented, and allows a oneshot solution for applying patches and configuration in one command.

I’m not sure how diff’ing against /dev/null is difficult

The number of contributors to OSMC’s kernel configuration is pretty low, but most are happy to work this out. I’m reluctant to make invasive changes to the build system when the effort->reward ratio would be so low. If you have a proposed patch, then I’d be keen to see it. I’m still looking forward to some pull requests from you to improve OSMC.