ALPM-PACKAGE-GROUP(7)

📦 version 0.13.0, in arch rolling

okay so real talk: this is the package group page from the Miscellaneous Information Manual, section (7), and it’s literally all about how ALPM based packages get grouped. no cap, bestie. 💅

✨ NAME ✨

package group — package grouping for ALPM based packages. that’s the whole name and it’s giving exactly what it says. 🎀

💅 DESCRIPTION 💅

okay so package groups are the way to describe arbitrary grouping for ALPM based packages. they show up in build scripts or file formats for package metadata — like PKGBUILD, PKGINFO or SRCINFO — to describe the groups a package belongs to. 🦋

package groups can be used for a bunch of reasons (e.g. “a group of all providers of a feature”, “a group of all text editors”), and fr fr no specific guidelines exist. software such as package managers can rely on package groups to list grouped packages and install as well as uninstall them in bulk. ✨

the value is represented by a UTF-8 string (e.g. my-group or my-other-group). even though it’s possible to use a UTF-8 string, it’s recommended to limit the value to the alpm-package-name format. package managers may use a package group to install an entire group of packages, and group names containing special characters or whitespaces may be confusing to users. 🙈

👀 Visibility of groups 👀

package groups solely exist as package metadata, and any package can be in zero or more of them. in the context of package management, package groups represent identifiers, that are visible across available package repositories, as they are defined by their members. 👑

⚠️ Caveats when relying on groups for installation ⚠️

package groups can be used by package managers to bulk install all ALPM based packages that are currently members of a given group. although in effect similar to meta packages when it comes to the bulk installation of packages, package groups are not package relations and are solely defined as a grouping mechanism! 🚨

when further packages are added to a given group, this does not result in them being installed automatically, as package management software merely evaluates the members of a group during a given installation action. aside from reinstalling all members of a group, there is no mechanism to stay in sync with the current members of a package group. 💀

🌸 EXAMPLES 🌸

the following PKGBUILD example defines a package that belongs to the group my-group. note that the created package carries the group name in its metadata (see PKGINFO for details). 🍓

pkgname=group-example
pkgver=0.1.0
pkgrel=1
pkgdesc="A package example"
arch=(any)
url="https://archlinux.org"
license=('GPL-3.0-or-later')
groups=(my-group)
depends=(bash)

package() {
  install -vdm 755 "$pkgdir/usr/share/doc/$pkgname/"
  touch "$pkgdir/usr/share/doc/$pkgname/test.txt"
}

🔗 SEE ALSO 🔗

💖 and that’s the cute sign-off, bestie: from the Miscellaneous Information Manual, section (7) — no version/date stamp appears on this one, so consider this your sparkly footer. 🫶

📦 where this page comes from