/etc/portage/package.keywords and wildcards

[garyd9]

I'm trying to find a simple way to tell emerge to accept the ~x86 keyword for all kde packages.. but without having to spell out each individual package thats in kde-base/

I've tried the following strings in package.keywords, but neither of them work:

kde-base/* ~x86
kde-base/kde ~x86

Is there any way to do this without specifying each individual kde-base/* package?

Thanks
Gary

[Carlo]

Not at the moment.


Carlo
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs.

[garyd9]

WELL THAT COMPLETELY SUCKS! GENTOO SUCKS! I WANT MY MONEY BACK.

Well, damn.. thats the FIRST thing I've seen that I can't do with gentoo. I'm actually a bit shocked.

Okay, I know there's an answer to this question somewhere, but for some reason I can't find it. Not sure if I can't find the right search keywords, or the daughter screaming in the background is distracting me...

I like doing "emerge kde". However, I neither need, nor want, anything in the "kdeedu" package. I also would prefer not having to re-edit files after every time I do an 'emerge sync'. I seem to remember that there's a way to mask kdeedu out of the 'kde' set of packages, but can't remember.. Any help?

Thanks
Gary

[LinuxRocks]

Well, I'm sort of a noob, but when I emrged 3.2.2, I just did an ACCEPT_KEYWORDS="~x86" emerge --pretend kde and it showed me what it was going to install. You can also substiture --pretend for search and it will show you all the versions, regular and masked. Then you can select. If you like the ACCEPT_KEYWORDS thing, then you can add it to the make.conf file and it will do it by default so you dont have to type it out all the time...

Thought I would through that in for ya

Joe

[tactless]

You don't mask it... you inject it (emerge inject category/package).

As for doing a keyword on an entire category... well, thinking about it, it makes perfect sense for kde or gnome, but what about the sys-apps category? That wouldn't work... I think the whole way gnome and kde appear in portage should be redone (subcategories! ), but such a change would be overkill for this particular problem...
_________________
Tactless

"If it wasn't for fog, the world would run at a really crappy framerate."

Jabber: tactless@amessage.info

[LinuxRocks]

What would the inject do?

Thanks!!!

Joe

[robmoss]

Try this:

[Carlo]

[Genone]

https://bugs.gentoo.org/show_bug.cgi?id=47192

[Gil-galad55]

Why was it decided that this feature was no good? Unless there's a shortcut around it, it makes mixing stable/unstable a true pain, and that makes testing a pain. Any thoughts on a workaround? I see a package.keywords that's laden with all the dependencies a fairly inelegant solution. The script below is fine for building said file, but it just seems klunky.
_________________
a^2 + b^2 = c^2
"To strive, to seek, to find, and not to yield." Tennyson

[Genone]

Main reason is to keep the syntax clean. There is no way that we support general regular expressions in the package.{keywords,use,unmask,mask} files (large performance impact, docs have to be rewritten, support becomes a nightmare, portage would have even more inconsistent syntax). Also for example the * operator has already a meaning for portage, so it would become ambigous with regexp support, same for other characters.
The only thing I would have supported is whole-category matching, but even that was shot down.

[tactless]

How about a special option to automatically arch-unmask all ebuilds that a certain ebuild RDEPENDS on? (Why do the kde and gnome ebuilds use RDEPEND anyway?)
_________________
Tactless

"If it wasn't for fog, the world would run at a really crappy framerate."

Jabber: tactless@amessage.info

[Gil-galad55]

[Carlo]

[Gil-galad55]

Ah, true, a middle man script. That would work nicely.
_________________
a^2 + b^2 = c^2
"To strive, to seek, to find, and not to yield." Tennyson