On 12/02/03 15:50:10, Mark Knecht wrote:
Thomas - thanks for responding. It all makes sense, but it isn't working out right as I try to get this cleaned up. I edited /var/cache/edb/virtuals to only have the two kernels called out that I have emerged
<SNIP> virtual/linux-sources sys-kernel/aa-sources sys-kernel/gentoo-sources <SNIP>
What does you virtual/alsa line say?
Currently I'm running 2.4.20-r7, but 2.4.20-r8 is merged. Maybe this is the problem? possibly I need to emerge -C r8 and emerge =r7 to get it perfectly in sync?
That shouldn't cause any problems, virtuals aren't version specific. So as long as you have an aa-sources kernel merged and running your virtual/ linux-sources shoudln't give you any trouble.
[ebuild N ] sys-kernel/development-sources-2.6.0_beta11 [ebuild N ] media-plugins/alsa-xmms-0.9.12
So, development-sources is not merged, and it's not under /usr/src, and it's no longer in /var/cache/edb/virtuals, but it's still getting pulled in. Why?
The only deps of alsa-xmms are xmms (obviously), alsa-lib and virtual/alsa for some reason portage feels the need to merge development-sources to satisfy virtual/alsa, the only thing I can think of that would cause this would be development-sources in virtual/alsa. If that isn't the case maybe someone more intimate with portage can shed some light on the problem.
-- Thanks, Thomas Achtemichuk
------------------------------------------------------------------------------- All newspaper editorial writers ever do is come down from the hills after the battle is over and shoot the wounded. -------------------------------------------------------------------------------
-- [EMAIL PROTECTED] mailing list
