On Sun, 2003-06-01 at 21:27, Peter Ruskin wrote:

> >
> > it would be nice to have a way to be able to run something like
> > emerge new-kernel
> > after compiling a new kernel. this could be done with an ebuilkd
> > variable that registers an ebuild as being dependant on the kernel?
> 

I think it would be nice to keep the alsa modules for more than one
kernel at a time (shouldn't be a problem, modules are in different
directories anyway). 

Couldn't the alsa-drivers ebuild just be changed so it doesn't unmerge
the modules, if I am gonna change kernel I would still have to manually
delete /lib/modules/x.x.x because of all the other modules not "managed"
b ebuilds. 

In my opinion the ebuilds shouldn't "control" kernel modules at all.

For me it is frustrating. I have at low latency patched kernel for audio
work, and another when I am not making music. It would be nice if I
didn't need to reemerge alsa-drivers, when switching between those
kernels.


Regards

Hasse Johansen