On Tue, 2003-12-02 at 10:48, Thomas Achtemichuk wrote:
> On 12/02/03 13:00:42, Mark Knecht wrote:
> > Hi,
> >    OK, I'm going completely buggy. I want to emerge alsa-xmms for my
> > 2.4.20-r7 machine, but emerge is telling me it wants to emerge
> > development-sources also. I do not have development-sources installed.
> > Why must I do this?
> 
> Because according to your virtuals file development-sources is providing  
> virtual/alsa support for your system. It may also be providing virtual/ 
> linux-sources.
> 
> To remedy this make sure you have your running kernel (2.4.20-r7) is merged  
> and that the virtual/alsa line in /var/cache/edb/virtuals lists media- 
> sound/alsa-driver before sys-kernel/development-sources and lists sys- 
> kernel/gentoo-sources before sys-kernel/developemet-sources on the virtual/ 
> linux-sources line.

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>

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?

Wizard root # emerge -p alsa-xmms

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[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?

>  
> >    Is there a simple way for me to stop this occurance at the command
> > line, or do I need to mask development-sources for some reason? Or do I
> > need to install it even though I don't use it? I'm seeing this alot with
> > Alsa packages recently, so I'm wondering if I have a make.conf option
> > set that's doing this?
> 
> What most likley happened is that you merged development-sources, unmerged  
> gentoo-sources then unmerged development-sources. Being the only installed  
> kernel at the time development-sources left itself as the only provider of  
> virtual/linux-sources and virtual/alsa. In order for this to not happen  
> again make sure you always have at least one kernel merged.

I don't think I ever had no kernels merged, but I KNOW that what is
merged is not always exactly what's running. 2.4.20-r8 came out, so it
got merged by not built. I possibly did emerge -C 2.4.20-r7 but I really
cannot remember exactly. It's not merged right now, even though the
source tree does exist under /usr/src

Wizard root # ls -l /usr/src
total 12
root  root   23 Sep 11 15:01 linux -> linux-2.4.20-gentoo-r7/
root  root 4096 Sep 11 15:08 linux-2.4.20-gentoo-r7
root  root 4096 Oct 25 07:52 linux-2.4.20-gentoo-r8
root  root 4096 Dec  1 22:29 linux-2.4.22-aa1
Wizard root # 

- Mark


--
[EMAIL PROTECTED] mailing list

Reply via email to