On Sunday 20 February 2005 06:08 am, Mark Knecht <[EMAIL PROTECTED]> wrote: > On Sun, 20 Feb 2005 04:11:35 -0600, Boyd Stephen Smith Jr. > <[EMAIL PROTECTED]> wrote: > > On Saturday 19 February 2005 08:28 pm, Mark Knecht > > <[EMAIL PROTECTED]> > > wrote: > > > On Sat, 19 Feb 2005 18:43:20 -0600, Boyd Stephen Smith Jr. > > > <[EMAIL PROTECTED]> wrote: > > > > On Saturday 19 February 2005 03:46 pm, Mark Knecht > > > > <[EMAIL PROTECTED]> > > > > wrote: > > > > > To compound this a bit I wanted to an emerge -e world on this > > > > > box in the coming week but the alsa-driver problem is there > > > > > still: > > > > > > > > > > gandalf root # emerge -ep world | grep alsa-driver > > > > > [ebuild N ] media-sound/alsa-driver-1.0.8 > > > > > > > > Can you do emerge --verbose -pet world and post the results? That > > > > will tell you what is bringing in alsa. > > > > > > Thanks Boyd. > > > > > > Of course the full results would probably be too much so here's 20 > > > lines before up to 8 or so lines after. If you need more let me > > > know. The full results zipped are around 8KB. > > > > Wow! Didn't realize it would be that big. > > emerge -e is pretty much everything, right? ;-)
Yeah, but it's just text! :) > > So, now we know which package needs to be removed from world. If you > > need help editing your world file, please ask. If this package is not > > in your world file, and you need more help, please follow-up with that > > information. If you do want alsa, but want it provided by the kernel > > sources, we may have to twiddle your virtuals, but I still know the > > solution. > > Prey tell, oh master, what is the solution? ;-) :P Didn't mean to sound too-smart-for-my-own-good there. Just, I've seen issues like those mentioned before. > Do I really want to remove anything from world? Or do I want to adjust > what the system thinks supplies things using virtuals? That seems more > correct to me. Well, you only want programs in world that you use directly; any deps will be pulled in automatically. So, if you don't use alsa-jack directly, take it out of world. > Looking at /var/cache/edb/virtuals it looks like the system really > believes that it needs alsa-driver to get alsa. How do I properly > change this to tell it alsa is in the kernel? Um, don't change this at all. You should change /etc/portage/profiles/virtuals. > virtual/alsa media-sound/alsa-driver A line like the above is in /usr/portage/profiles/base/virtuals. > Looking around in virtuals I also found this line: > > virtual/linux-sources sys-kernel/aa-sources The relevant line for me is: virtual/linux-sources sys-kernel/gentoo-sources from /usr/portage/profiles/default-linux/x86/virtuals > Since we now run gentoo-dev-sources it seems I should change this > line, and if that's true then I know the syntax for the alsa-driver > problem also. Is this correct? > > virtual/linux-sources sys-kernel/gentoo-dev-sources > virtual/alsa sys-kernel/gentoo-dev-sources Looks good to me. Just make sure you put it in the right file. > And then further, why is the entry for headers pointing to > linux-headers instead of linux26-headers? That's the default. Just like gentoo-sources (not gentoo-dev-sources) is the default kernel. When 2.6 becomes the default, it will be my unmasking those versions of the kernel as gentoo-sources, not by changing this line in everyone's profile. > virtual/kernel sys-kernel/linux-headers > > gandalf root # qpkg -I | grep headers > media-sound/alsa-headers * > sys-kernel/linux26-headers * > gandalf root # > > Seems that possibly I should change that also? Sure, that's fine. Something like: virtual/kernel sys-kernel/linux26-headers > None of this seems like magic. Portage/emerge is really very sensible, > but I don't want to make too many changes here. Maybe there's a Gentoo > docs page that talks more about these changes? Since virtuals is small > I'm attaching a proposed version with 4 edits: I wouldn't mess with the virtual file in /var/cache it's probably not really user-servicable. :) As man portage says (but not too clearly) you can override your current profile's virtuals with /etc/portage/profiles/virtuals; that's what you should edit/create. Virtuals only affects what actual package portage chooses for a virtual when nothing installed currently provides that virtual, however this can subtley interfere with emerge -e (since not is considered installed, nothing can provide the virtual) and emerge XXX YYY when XXX depends on a virtual provided by YYY and YYY is not the default provider. > virtual/linux-sources sys-kernel/gentoo-dev-sources > virtual/os-headers sys-kernel/linux26-headers > virtual/kernel sys-kernel/linux26-headers Fine. > virtual/alsa media-sound/gentoo-dev-sources Um, I'm pretty sure you want sys-kernel/gentoo-dev-sources and not media-sound/gentoo-dev-sources (which doesn't exist). Those four lines can then be added to /etc/portage/profiles/virtuals (existing lines for the same virutals removed/commented) or can be the whole of a newly created etc/protage/profiles/virtuals. I wish the handbook went into more detail on virtuals. I believe you should set your virtuals before you bootstrap, especially items like virtual/os-headers. After you does any world file cleaning you need to and have set you virtuals the way you want them, try the emerge --verbose -pet world against and, if there are any more problems, we'll work for there. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- [email protected] mailing list
