The concept of a meta ebuild, also referred to as a meta package, exists in the Gentoo ebuild repository and other ebuild repositories. These ebuilds typically include the term "meta" as a naming suffix, although doing so is not a requirement of a Gentoo development standard (such as the EAPI, GLEPs, or the developer manual). Not all meta-style ebuilds use the same terminology.
A meta ebuild is an ebuild containing a developer-selected, curated software suite that generally relates to a certain family of related software packages. Many meta ebuilds do not install any files themselves, but are used to reference the installation requirements for a family of related software packages.
Some meta ebuild examples include:
|Meta package for GNOME, merge this package to install.
|Includes a maximalist packages set for the GNOME desktop environment. Review the various USE flags for this package to adjust features included with GNOME.
|Meta package for GNOME-Light, merge this package to install.
|Includes a minimal package set for the GNOME desktop environment.
|Meta package for coreapps (C Suite).
|Available from the ::guru ebuild repo.
|Merge this to pull in all KDE Plasma 5 packages.
|Meta ebuild for LXDE, the Lightweight X11 Desktop Environment.
|Meta ebuild for LXQt, the Lightweight Desktop Environment.
|Meta package for fonts to cover most needs.
|This ebuild includes an
emoji USE flag, which is very useful for systems starting a desktop (graphical) profile.
|Meta ebuild to pull in gst plugins for apps.
|Review the various USE flags for this package.
|The Xfce Desktop Environment (meta package).