pkgbase: treat all the kernel packages the same way

[bapt]

Summary

Install the GENERIC kernel into /boot/kernel.GENERIC

[bapt]

fix Unassociated shell command

[bapt]

fix make distributekernel

[zlei]

Makefile.inc1

1831

Will this have impact on boot loader ?
The default kernel is /boot/kernel/kernel .

$ grep -r '/boot/kernel/kernel' stand
stand/man/loader_simp.8:boot /boot/kernel/kernel
stand/man/loader_4th.8:boot /boot/kernel/kernel
stand/man/loader_lua.8:boot /boot/kernel/kernel
stand/efi/loader/main.c: * /boot/kernel/kernel (the default kernel) that we can use.

During daily dev I have multiple kernels and I workaround this by

# ln -s kernel.stable14 /boot/kernel

CC @imp .

[kevans]

Makefile.inc1

1831

hmm, I thought I had a patch to stop adding /boot/kernel/kernel automatically if it doesn't actually exist; looks like I need to find that.

[imp]

I think this is fine, but I might be missing something...

Makefile.inc1

1831

I thought so too...

The default search order is /boot/kernel;/boot/modules (and maybe /boot/dtb).

But it looks like kernel_path/module_path env overrides this. And we set that from lua/config.lua... and it looks like it's trying to find things, so it might already be committed.

All that the grep shows is that we document /boot/kernel/kernel as the default.

[kevans]

Makefile.inc1

1831

Looks like not, the logic is a bit twisty... the part in question is in core.kernelList(): we'll take the default kernel, which is "kernel", and add it first- then we'll autodetect kernels but we won't note the presence (or lack thereof) of the default kernel.

Somewhere, probably in one of my stash entries, there's a patch that notes the presence of it and removes it from the list if it's missing, but only if it's "kernel" inherited from the kernel env var. If it's instead in the kernels list, I assume someone did that intentionally and we leave it alone since kernels is empty by default.