On Fri, Jan 25, 2013 at 2:19 PM, Christopher Head <ch...@chead.ca> wrote: > Surely even that isn’t good enough, since the user could have built an > option as a module, tested it out, discovered it worked fine, and then > rebuilt the kernel with the option set to Y, but the .ko file would > still be left lying around?
Yup. Until the day comes when we have a USE flag for every kernel parameter (in both built-in and module form) and just have the ebuild actually build and install the kernel, it is going to be messy. The kernel is a bit unique in that we just dump a pile of source on the disk and ask the user to have at it. Note that I'm by no means advocating that we actually do any of that - the kernel is unusual in that it is EXTREMELY configurable otherwise this is probably what would have been done. As I mentioned in my last email maybe having a kernel package that does do exactly that for a desktop-oriented kernel with maybe only a few USE options might not be a bad idea - perhaps even managing grub config and all. That could be something that would make life easier on users who don't care to customize their kernels. Rich
