| Title: | Handling kernels with portage |
|---|---|
| Version: | 1.1 | +
| Version: | 1.2 |
| Last-Modified: | 2004/05/03 01:48:45 | +
| Last-Modified: | 2004/11/11 21:32:21 |
| Author: | Nathaniel McCallum <npmccallum at gentoo.org>, Joshua Campbell <warpzero at gentoo.org> |
| Status: | Draft | +
| Status: | deferred |
| Type: | Standards Track |
| Content-Type: | text/x-rst | +
| Content-Type: | text/x-rst |
| Created: | 2-May-2004 |
| Post-History: | 2-May-2004 | +
| Post-History: | 2-May-2004, 11-Nov-2004 |
Timed out
+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.