[linux-yocto] KMETA branch/directory redux (yocto #5090)

[Peter A. Bigot]

First, some yak shaving:

If something goes wrong with linux-yocto's do_patch, it prints:

| ERROR. Could not apply patches for beaglebone.
|        Patch failures can be resolved in the devshell (bitbake -c 
devshell linux-yocto)

In fact, you can't, because meta/classes/devshell.bbclass has:

addtask devshell after do_patch

so there's a chicken/egg thing here because bitbake never gets to 
devshell.  No idea how to fix that.

Now: What goes wrong with do_patch for me ultimately turns out to be 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5090 biting me again a 
year after I filed and forgot it, because I set KMETA=yocto-3.14/meta 
because that's the branch name in my local kernel directory.  Various 
kgit-* tools still want to use KMETA to name the directory as well as 
the branch, and they are not happy when KMETA isn't meta.

I'm going to try to do a patch for that, if it's agreed that KMETA 
really does only name the branch and something else needs to propagate 
the directory name among all the scripts.

Before I do that, is that the intended behavior?  I was going to add 
KMETA_DIR as the companion variable, and probably have all the 
meta_dir() shell functions in the *me scripts export that.

Are patches to yocto-kernel-tools to be sent to this list?

Also, is there a reason all the support scripts are present in the 
meta/scripts directory of the KMETA branches, even though when you run 
bitbake the versions that come from kern-tools are the ones that are 
actually used?  Their presence tricked me into thinking that the ones in 
the meta branch were what I should be patching....

Peter