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
