With the 2.6 kernels, alsa is now a part of the kernel source tree(s), and thus the alsa-driver ebuilds should be obsolete for 2.6 users (?). The alsa-util ebuilds, however, still depend alsa-driver.
What is the appropriate way to handle this? Are the ebuilds being reworked to handle this discrepancy. emerge -pU world now wants to install alsa-driver-0.9.2. Should I just inject this package to prevent the update? Is this going to be resolved in a more standard fashion? -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
