Search:  
Gentoo Wiki

Meta_Ebuild

How the meta ebuild works

A meta ebuild is a ebuild that doesn't install files by itself, but instead it's used to install a group of other ebuilds with 1 command. It accomplishes this by having all this other ebuilds as dependencies. A example of a meta-ebuild is 'kde-meta'. To preview the packages that make up kde-meta with all their USE-flags do this:

# emerge kde-meta -vp

If you were to actually emerge kde-meta, those are all the packages that would be installed to fulfill kde-meta's dependencies. To install kde and all its dependencies re-enter the command without the pretend option, '-p':

# emerge kde-meta

As said above, kde-meta depends on all the individual packages of kde. So when you check the list of required packages, and find that 'kde-meta' is not a real package, its a metapackage. Also, since the meta ebuild has the kde stuff as dependencies, doing this:

# emerge --unmerge kde-meta

Will not remove ALL of kde, it will only remove the metapackage that depends on the kde packages. However, this will make them unnecessary (at least portage thinks so) and therefore doing:

# emerge --depclean -p

CAUTION! depclean without -p can SERIOUSLY damage your system
will show kde packages, because the metapackage that depended on them are gone.

See also

Retrieved from "http://www.gentoo-wiki.info/Meta_Ebuild"

Last modified: Wed, 26 Dec 2007 13:59:00 +0000 Hits: 13,414