On Thu, 2004-01-08 at 21:45, Mark Knecht wrote: > Why? If the directories are both there, why doesn't Alsa still work for > both? Maybe I'm doing something wrong somewhere that I need to learn > about. >
What is happening is the emerge command is removing the previous modules when it cleans up the previous install. This is being changed in a future version of portage. However, until then, here is a workaround: 1. Build 2.4.20-r1 2. emerge alsa-driver 3. Build 2.4.20-r5 4. env CONFIG_PROTECT="/lib/modules/2.4.20-r1" emerge alsa-driver By temporarily adding the directory to the CONFIG_PROTECT variable, you are ensuring that portage will not touch anything in that directory. I don't recommend adding this to the make.conf file, since you normally want the current portage behavior, except in this situation. You can also do what BillK suggested and touch the files to change the timestamps. I prefer to use the CONFIG_PROTECT option as I *know* that portage won't delete the files in this case. However, the advantage of touching the files is that you don't have to remember to do it every time you run the emerge command. Using the CONFIG_PROTECT variable is something that you need to remember to do every time. -- My Gentoo stuff: http://varnerfamily.org/pvarner/gentoo -- [EMAIL PROTECTED] mailing list
