> On Fri, Sep 12, 2003 at 09:23:58AM -0700, Mark Knecht muttered: > > Hi, > > Does my local emerge and/or portage keep separate databases for each > > kernel with different patch levels? I know it doesn't for minor > changes like > > 2.4.20-r6 vs. 2.4.20-r7, but what about 2.4.20 vs. 2.4.22 or 2.6.x? > > > > I don't want to start fixing problems on my new 2.4.22 > kernel, only to > > discover I'm creating problems for a perfectly working 2.4.20-r7 > > installation. > > AFAIK, all Portage'll do for you on kernels is just unpack the source > into /usr/src/linux-x.y.z-w. Modules are handled by the kernel > build -- it puts > modules in (IIRC) /lib/modules/x.y.z-w -- so if the version number is > different, the modules won't conflict. > > -- > Andrew Farmer
Andrew, Sorry. I guess me question wasn't clear. I agree. All portage does with kernels is unpack source and modify it's database to say it's installed. My question was really one about lower level executables like Alsa. Is emerge able to keep track of which kernels I have built Alsa for and which I have not? Look at this flow: 1) I run 2.4.20 and install Alsa. It's working and the files are in /lib/modules/2.4.20. 2) I boot into 2.4.22. Alsa doesn't work. I then emerge -C alsa-drivers. Now the database says alsadrivers is not installed. 3) Then, instead of emerging alsadrivers, which would make sense, I boot back into 2.4.20. Emerge tells me that alsa-drivers is not installed, but Alsa still works since the files are still in /lib/modules/2.4.20 Is this correct? At this point the portage database thinks alsa-drivers is gone, but it isn't for this kernel. It's only gone for 2.4.22. Correct? This means if I then do an emerge --update --deep world for 2.4.20 that it's going to emerge alsa-drivers again? I wouldn't if portage kept a separate database for each kernel. Thanks, Mark -- [EMAIL PROTECTED] mailing list
