Re: [gentoo-dev] Speaking of new kernels being added to the tree

[Luke-Jr <luke-jr@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 04 October 2003 04:29 am, Jason Stubbs wrote:
> However, having portage compile and install Linux has several issues.
> Portage would need  to be able to:
> 1) handle multiple saved configurations automatically.
Perhaps there could be a KERNEL_CONFIG option which looks for a different 
config file for genkernel w/ KERNEL_CONFIG appended and then appends 
KERNEL_CONFIG to the output kernel. SLOTting this could allow one to install 
it multiple times with different KERNEL_CONFIG.

> 2) update lilo/grub automatically _with_ backup.
I don't think it's the backups that would be complex to do, but the updating 
of lilo/grub automaticly. Does it really need to be done, though? The ebuilds 
could theoreticly manage a set of symlinks /boot/{kernel,initrd}{,-
{current,previous}} (also a {kernel,initrd}-working which is set after a user 
successfully logs in?) and let the user determine whether to use them or to 
manually manage their kernel config.

> 3) extract the source to /usr/src if need be (as already mentioned)
> 4) handle different configurations of the same kernel version.
>
> Tangible benefits that I can see:
> 1) ccache can be used in compiling the kernel automatically
I don't see that ccache is all that great. I'd much rather Portage leave the 
original /var/tmp/portage/*/work directories when remerging a package so they 
can reuse the object files that are still consistant.

> 2) a lot of disk space can be saved.
- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/fsXAZl/BHdU+lYMRAkO0AJ43/WiVjCwX8qvFwjTaaFcHd7kjugCglWCz
RIZAXPj6dXTvAm2S83yw2lg=
=/RpY
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list