Emerge, keywords, dependancies

[Spacefreak]

I am getting seriously mind raped right now. I've managed to stay relatively not clueless on pretty much everything I've done up to trying to get kde 4.2 installed. However, my confusion really don't come from kde 4.2 at all. It's all centered around emerge. I don't really feel like changing my portage to 2.2, it seems a somewhat important feature to be changing it to a non-stable version.

So, I can't use sets, and I'm not quite sure how to do the package.keywords properly. I noticed that adding the contents of the program's keywords to the /etc/portage/package.keywords file will make them available. Then I run into dependency issues.

So, first, when it comes up that I have dependency issues, can I change the command to just install all dependencies first and then the program in question? Or do I have to go through and do each program individually as it tells me?

Now, I tried the second option, since I didn't know how to do the first, and that program needs a keyword too. It's my understanding that you can use the package.keyword system as a folder instead of a file, which I think would be fabulous, since I don't have a graphical interface just yet, and I'm not exactly sure how to go about copy-pasting the contents of one and merging it with another in the package.keywords file. The tutorial goes through how to do it, but it calls everything foo. I realize this is common language, but it still confuses me. For instance, it says:

# mkdir -p /etc/portage/package.keywords # yes we create a directory not a file!!!
# echo "foo/foo" > /etc/portage/package.keywords/foo # the name for the file can be chosen freely
# echo -e "foo/foobar \nfoo/barbar" >> /etc/portage/package.keywords/foo

There so many foo/foobar/nfoo/barbar that I'm not sure what each is referring to honostly. Some seem arbitrary, some seem like they should be one specific thing for each program. Seems like everytime I have a question in gentoo and I manage to solve it, I'm really just openning up a completely different can of worms. Any help would be greatly appreciated.

[yngwin]

Start by studying the Handbook: http://www.gentoo.org/doc/en/handbook/index.xml especially the Working with Gentoo and Working with Portage parts.

[NeddySeagoon]

Spacefreak,

It sounds like you are badly in need of autounmask. emerge autounmask and it can be used to populate your package.keywords.

Traditionally, /etc/portage/package.keywords was a file with one entry per line.
Now it may be a directory, in which case, all the files it contains are concatenated together. The file names do not matter and are not significant to portage. They probably should be to you though, since you will need to find your way around later on.

[nmp0906]

KDE4 is a pain when you don't realize tools like autounmask are available. You unmask one package, just to follow with another dependency. 50 unmasked packages and an hour later you get a clean emerge. Now if I'm not mistaken KDE4.2 is not masked, it is just marked as unstable (ie. use package.keywords instead of package.unmask). In this case, the solution is simple for the time being:

Code: Select all

# ACCEPT_KEYWORDS=~arch emerge -av kde-meta

Also, if I remember correctly, since this uses EAPI2, you will have to upgrade portage to the latest unstable version (I had to for KDE 4.1, don't know what the deal is now with 4.2). Anyways, add sys-apps/portage to your package.keywords file (or a file in that directory) and re-emerge it. No big deal, portage unstable has worked fine for me since I built my system.

[yngwin]

KDE4 is a pain when you don't realize tools like autounmask are available. You unmask one package, just to follow with another dependency. 50 unmasked packages and an hour later you get a clean emerge.

There is no need for that. Just follow the KDE4 guide and grab the package.keywords file that is linked to in the guide.

In this case, the solution is simple for the time being:

Code: Select all

# ACCEPT_KEYWORDS=~arch emerge -av kde-meta

This is very, very, very bad advice. On a next world update all those packages would be downgraded again. You need to add them to your package.keywords. This is easy, and with the provided file from the guide it is very easy and (almost) foolproof.

Also, if I remember correctly, since this uses EAPI2, you will have to upgrade portage to the latest unstable version (I had to for KDE 4.1, don't know what the deal is now with 4.2).

No, not at all. The latest stable portage (2.1.6.x) supports EAPI=2 just fine.

I appreciate you want to help another user. But please get your facts straight before you confuse them...

[nmp0906]

KDE4 is a pain when you don't realize tools like autounmask are available. You unmask one package, just to follow with another dependency. 50 unmasked packages and an hour later you get a clean emerge.

There is no need for that. Just follow the KDE4 guide and grab the package.keywords file that is linked to in the guide.

Absolutely. Just sympathizing in the case where you don't have a file handed to you. I did a KDE4 install last year without following the guide.

In this case, the solution is simple for the time being:

Code: Select all

# ACCEPT_KEYWORDS=~arch emerge -av kde-meta

This is very, very, very bad advice. On a next world update all those packages would be downgraded again. You need to add them to your package.keywords. This is easy, and with the provided file from the guide it is very easy and (almost) foolproof.

Agreed. I use this mostly to get a list of what would be installed without it stopping me on every package. In a hurry, you can use it get through an emerge, but its better used to previews and for even making your own package.keywords. I should have clarified.

Also, if I remember correctly, since this uses EAPI2, you will have to upgrade portage to the latest unstable version (I had to for KDE 4.1, don't know what the deal is now with 4.2).

No, not at all. The latest stable portage (2.1.6.x) supports EAPI=2 just fine.

I appreciate you want to help another user. But please get your facts straight before you confuse them...

My apologies. I remember having this issue when I did a KDE4 install with the stable version of Portage. You called me on an improper assumption.