I disagree, when dealing with a ~x86-package it might have deep-dependencies that is also in ~x86.
I also disagree on package.keywords since it's better to test if emerge goes well and that module actually works before making any static changes regarding keywords or even USE- & FEATURES-flags for that matter. /©harlie On Wed, January 12, 2005 10:37, Eugene Rosenzweig said: > I don’t like using ACCEPT_KEYWORDS, it makes emerge try and install all > sorts of packages > with -D option. Better way is to put > > net-wireless/ipw2200 ~x86 > > line into /etc/portage/package.keywords. > > See portage manpage for more info. > > Eugene. > >> -----Original Message----- >> From: Charlie Gehlin [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, 12 January 2005 7:58 PM >> To: [EMAIL PROTECTED] >> Subject: RE: [gentoo-user] WiFi success story :| >> >> Try: >> >> 'ACCEPT_KEYWORDS="~x86" emerge -Dv ipw2200' >> >> /©harlie >> >> On Wed, January 12, 2005 8:25, Schafer Frank said: >> > ipw2200 is masked by ~x86 keyword. How did you unmask it? I've tried >> to >> > put wpa_supplicant to package.unmask too and it remains masked. >> > >> > ... but anyway, thanks for the hint. >> > >> > Frank >> > >> > -----Original Message----- >> > From: Martin Büchler [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, January 11, 2005 4:46 PM >> > To: [EMAIL PROTECTED] >> > Subject: Re: [gentoo-user] WiFi success story :| >> > >> > unmask ipw2200, then there is no need for building the driver >> yourself. >> > >> > i've got it here on my laptop, and it works like a charm. (asus >> travelmate >> > 6002lmi, kernel 2.6.9) >> > >> > mfg martin >> > >> > On Tue, 11 Jan 2005 09:35:01 -0700 (MST), Ric Messier >> <[EMAIL PROTECTED]> >> > wrote: >> >> >> >> On Tue, 11 Jan 2005, Ric Messier wrote: >> >> >> >> > >> >> > On Tue, 11 Jan 2005, Schafer Frank wrote: >> >> > >> >> >> >> >> >> What will I have to do to change from simpleinit to sysv init? >> >> >> Would it be sufficiennt to emerge sysv? Will I have to unmerge >> >> >> simpleinit? I'd like to have my initscripts #!/bin/sh. >> >> >> >> >> > >> >> > Is that the only reason you want a SysV init? A bit odd, especially >> >> given: >> >> > >> >> >> >> Thinking about this further, I'm even less sure about the problem you >> >> are trying to solve. You might check to see whether sysvinit is >> >> already installed as I seem to recall it's part of the base system. I >> >> know it's installed on my system and I never asked for it explicitly. >> >> >> >> Ric >> >> >> >> -- >> >> gentoo-user@gentoo.org mailing list >> >> >> >> >> > >> > -- >> > gentoo-user@gentoo.org mailing list >> > >> > >> > >> > >> > -- >> > gentoo-user@gentoo.org mailing list >> > >> > >> >> >> >> -- >> gentoo-user@gentoo.org mailing list >> > > > > -- gentoo-user@gentoo.org mailing list
