[gentoo-user] Re: mone on the KEYWORD USE front

[gentoo-user] Re: mone on the KEYWORD USE front

[Michael Mauch]

reader@newsguy.com wrote:

> This makes you want to use ACCEPT_KEYWORDS on the command line, but
> after seeing the reasons for not doing that in recent posts I decided
> to follow the suggestions, and not do it.
> 
> So either you must cycle thru enough `emerge -v kde' to find all
> packages needing unmasking and do it in /etc/portage/package.keywords
> or maybe in /etc/make.conf with `ACCEPT_KEYWORDS=~x86'.  

What about

  ACCEPT_KEYWORDS="~x86" emerge -p kde-meta

and then copy the whole list to /etc/portage/package.keywords?

  ACCEPT_KEYWORDS="~x86" emerge -p kde-meta | 
  gawk '/\[ebuild/ {sub(/[^]]+\] /,"");sub(/-[0-9].+$/," ~x86");print}'


  Michael
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] mone on the KEYWORD USE front

[reader]

Just when I was thinking I might finally be getting a handle on using
keywords and USE variable to control my install, I discover it really
isn't as nifty as one might think.

Here is my case:

I grew tired of all the ins and outs of kde installation although I
had a working one.  I decided to scrap it all and start with just 3.5
stuff.

Well you might think all that would be necessary is to keyword either:

 kde-base/kdebase ~x86
 kde-base/kde-meta ~x86
 kde-base/kde ~x86

Which you would think would allow a full install of kde-3.5 in one of
those areas.  But it will not.

What happens is emerge runs into a whole long list of other kde
packages that themselves must also be keyworded. but it only shows
them one at a time.   Telling user one package is masked and to read
the manpages to proceed.  Having keyworded that one trying to preceed
finds another.... and another..... etc.

I'm not sure how many ... I gave up after just a few thinking it was
really a tedious way to find what needs keywording.

This makes you want to use ACCEPT_KEYWORDS on the command line, but
after seeing the reasons for not doing that in recent posts I decided
to follow the suggestions, and not do it.

So either you must cycle thru enough `emerge -v kde' to find all
packages needing unmasking and do it in /etc/portage/package.keywords
or maybe in /etc/make.conf with `ACCEPT_KEYWORDS=~x86'.  

The make.conf route also seems it might have far reaching
implicaitons.  And I suspect it would have some repercussions
unthought of to just remove it after emerging kde.  Like maybe any deps
brought in would suddenly need to be replaced by the masked packages.

So is there a more elegant solution than doggedly running 
emerge -v kde until all packages needing unmasking have been
revealed and entered into /etc/portage/package.keywords?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mone on the KEYWORD USE front

[Richard Fish]

On 12/15/05, reader@newsguy.com <reader@newsguy.com> wrote:
> Well you might think all that would be necessary is to keyword either:
>
>  kde-base/kdebase ~x86
>  kde-base/kde-meta ~x86
>  kde-base/kde ~x86

Nope, you have to keyword-accept the dependancies also...

> What happens is emerge runs into a whole long list of other kde
> packages that themselves must also be keyworded. but it only shows
> them one at a time.   Telling user one package is masked and to read
> the manpages to proceed.  Having keyworded that one trying to preceed
> finds another.... and another..... etc.

Try:

ACCEPT_KEYWORDS=~x86 emerge -pv kde-meta

The above should tell you all dependant packages that you will need to
add to /etc/portage/package.keywords.

> This makes you want to use ACCEPT_KEYWORDS on the command line, but
> after seeing the reasons for not doing that in recent posts I decided
> to follow the suggestions, and not do it.

You don't want to use it without the --pretend option.  There is no
problem at all with specifying environment variables on the command
line just to investigate their effects though.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mone on the KEYWORD USE front

[Chris White]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

On Friday 16 December 2005 09:54, Richard Fish wrote:

echo "x11-libs/qt" >> /etc/portage/package.keywords ; 
cd /usr/portage/kde-base ; for packages in * ; do	echo "kde-base/${packages}" 
>> /etc/portage/package.keywords; done

Chris White

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] mone on the KEYWORD USE front

[Dale]

reader@newsguy.com wrote:

>
>So is there a more elegant solution than doggedly running 
>emerge -v kde until all packages needing unmasking have been
>revealed and entered into /etc/portage/package.keywords?
>
>  
>
Well, you could ask someone to share theirs.  LOL  Look at this thread:

http://forums.gentoo.org/viewtopic-t-407352.html

That may help a bit.

Dale
:-)

-- 
To err is human, I'm most certainly human.

I have four rigs:

1:  Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives.  
2:  Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
3:  Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB drive.
4:  Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive.

All run Gentoo, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.  

-- 
gentoo-user@gentoo.org mailing list