On Tue, 2003-07-15 at 11:28, Michael Schreckenbauer wrote: > I think a ACCEPT_KEYWORDS="~86" emerge -p alsa-driver would do the trick. > You can always look in /usr/portage/<category>/<package> to see, if there are > updates to packages you are interested in. >
Hi, Looks like I'm still confused. Maybe I have some larger configuration issue? Maybe there's some setting in /etc/make.conf that makes this come out different? On my test machine at work the proposed command: ACCEPT_KEYWORDS="~86" emerge -p alsa-driver finds alsa-driver-0.9.5-r2, but on the machine here in my studio it does not, even though the ebuild does seem to exist in /usr/portage/media-sound/alsa-driver: Wizard root # ACCEPT_KEYWORDS="~86" emerge -p alsa-driver These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild UD] media-sound/alsa-driver-0.9.2 [0.9.4-r1] Wizard root # bash-2.05b$ pwd /usr/portage/media-sound/alsa-driver bash-2.05b$ ls ChangeLog alsa-driver-0.9.3c-r1.ebuild Manifest alsa-driver-0.9.3c.ebuild alsa-driver-0.5.12a.ebuild alsa-driver-0.9.4-r1.ebuild alsa-driver-0.9.0_rc2.ebuild alsa-driver-0.9.4.ebuild alsa-driver-0.9.2.ebuild alsa-driver-0.9.5-r2.ebuild alsa-driver-0.9.3a.ebuild files alsa-driver-0.9.3b.ebuild bash-2.05b$ Or do I need to do the 0.9.4 update before it will find 0.9.5-r2? The test machine does not currently have alsa inastalled at all, and it found 0.9.5 first try. I be con-fu-sed...feeling stupid...sorry. Thanks much in advance, Mark -- [EMAIL PROTECTED] mailing list
