Bug 129087

Summary:	Feature Request: Unmasking metapackage unmasks dependencies
Product:	Portage Development	Reporter:	Travers Buda <traversbuda>
Component:	Core - Dependencies	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WONTFIX
Severity:	enhancement	CC:	jakub, m.debruijne
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Travers Buda 2006-04-06 22:59:31 UTC

For an example, I will use xorg-x11-7.0-r1 which is curently ~ on all arches. As you know, this xorg-x11 ebuild is a metapackage for the modular X.org.

It would be really nice to be able to unmask a metapackage (xorg-x11 ~amd64 in /etc/portage/package.keywords) and have portage automagically unmask all the dependencies.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-04-07 00:23:05 UTC

From portage point of view, metabuild is no different than a normal ebuild. Automagic unmasking of dependencies for whatever package you put into p.unmask is a bad idea. Which dependencies would you like to unmask, the direct ones? Or the indirect ones as well? Pretty much defeats the whole point of package.mask. It isn't there to make your life easier, it's there to prevent possible damage to your system.

Comment 2 Alec Warner (RETIRED) archtester

2006-05-11 17:44:54 UTC

Emerge will not do this, write a script/tool.