Am 05.07.2012 01:58, schrieb Rich Freeman: > About the only really "safe" approach would be to run as a limited > user, install it into some offset/chroot, package it, and then > install it using portage as a binpkg. That actually has advantages > on many levels, and it basically is what we do with everything else.
I think that's a good idea to have a script which packs the needed files (kernel) and modules into a binpkg: - define KBUILD_OUTPUT - after emerging the sources (or downloading), configure and build your kernel - launch a script which 'installs' the modules and also the kernel in a sandbox like portage normally does and generates a binpkg with a given version number (or auto generated based on kernel version) - install the binpkg (or advise the script to do so) this has the advantage, we can build the kernel as user and also have all installed files recorded by the package manager (which is unfortunately not the case with the current approach) which makes removing them much easier (only remove -source- and/or -bin- pkg) /martin