#29 Advanced Emerge UI needs work with masked packages

[Anonymous]

IMHO, a user shouldn't have to click on Advanced Emerge
to compile a masked package. Rather if all ebuilds are
masked, Porthole should prompt saying so and allow the
user to override in this case.

Also, under the Advanced Emerge dialog, why is there a
radio button for which keyword to accept? Shouldn't it
just have either x86 vs ~x86 (or ppc vs ~ppc, etc)? I
don't think I ever want to select ~ia64 on my Mac
running Gentoo....

[Brian Dolbec]

Logged In: YES
user_id=953915

That is a good idea. Although we do have a popup menu in
the package view now thanks to Tommy, which has a option to
add the package to the keywords file.

Another option would be to disable the emerge button when a
keyword masked package is selected. That would tend to
encourage the user to add the package to the
package.keywords file to re-enable the emerge button/menu items.

As for the advanced emerge dialog. The developer that
created it wanted to keep all the options open and
available. That way if someone was doing cross-compilation
that option was available.

I have been thinking of ways to shortcut it. Perhaps I
could add a "Enable-cross compilation keywords"
configuration option which would default to "no". That
would give the desired effect for most users.