On Mon, 17 Jan 2005 08:41:00 -0500, Chris Gianelloni
<[EMAIL PROTECTED]> wrote:
> On Sun, 2005-01-16 at 17:30 +0000, John Mylchreest wrote:
> > As I requested in a previous post, it is there for a few reasons. It is
> > a key phase in automating the process of kernel upgrades. For example..
> >
> > something along the lines of:
> >
> > #!/bin/bash
> > USE="symlink" emerge ${1:-sys-kernel/gentoo-sources}
> > genkernel --no-menuconfig --install
> > for I in $(</var/lib/modules)
> > do
> > module_list="${module_list} ${I}"
> > done
> > emerge --nodeps ${module_list}
> >
> > and that module list is populated (or removed) when the user
> > merges/unmerges a module. (postinst, postrm)
> >
> > will download, compile and install a new kernel, and all modules which
> > are currently on the system.
> >
> > As I also suggested in a previous post, if you can think of a more
> > intuitive way for the user to be able to do this, without the use of a
> > USE flag which is persistent and doesn't involved an external file,
> > please. Let me know. If its viable, I will migrate the functionality to
> > that.
>
> Honestly, what it sounds like you're planning for is a portage feature,
> not an optional component. You might do better with something like
> FEATURES=autokernel or something.
I for one would like to see such functionality. Since we have
genkernel, it shouldnt be hard to implement. Should it?
>
> --
> Chris Gianelloni
> Release Engineering - Operational/QA Manager
> Games - Developer
> Gentoo Linux
>
>
>
--
gentoo-dev@gentoo.org mailing list
