--- xml/htdocs/proj/en/glep/glep-0026.html 2004/05/03 01:49:48 1.1 +++ xml/htdocs/proj/en/glep/glep-0026.html 2004/11/11 21:32:30 1.2 @@ -8,7 +8,7 @@ -->- +
|Title:||Handling kernels with portage|
|Author:||Nathaniel McCallum <npmccallum at gentoo.org>, Joshua Campbell <warpzero at gentoo.org>|
Currently, the only automated kernel build proceedure that we have is genkernel. While genkernel is a great tool, its main weakness is that it does not port well to other arches because of the initrd and the lack of good "generic" settings for other arches. @@ -80,7 +85,7 @@ implementing the most common aspect (the build proceedure) into a portage eclass.
There would be 3 layers to kernel building: (place of implementation)
@@ -151,7 +156,7 @@
There are many advantages gained by this method:
@@ -169,25 +174,25 @@ we can either make portage build kernels or we can make genkernel build everything else.
If you want to emerge kernel sources the old way, just do: USE="-buildkernel" emerge kernel-name
Perhaps we could also name the new kernel-config program (from Stage 1) "genkernel" so that users can have a seemless transition.