DNF4-GROUPS-MANAGER(8)

πŸ“¦
version 4.7.0 Β· 3 versions
, in centos-stream 10

✨ NAME ✨

hiii bestie πŸ’– welcome to DNF4-GROUPS-MANAGER(8), aka the dnf4-groups-manager page from dnf-plugins-core. it's the DNF groups-manager Plugin, and its whole thing is creating and editing groups repository metadata files. yes ma'am, groups metadata. πŸŽ€

πŸ“œ SYNOPSIS πŸ“œ

dnf groups-manager [options] [package-name-spec [package-name-spec ...]]

🌸 DESCRIPTION 🌸

the groups-manager plugin is literally how you create or edit a group metadata file for a repository. it's often way easier than writing/editing the XML by hand β€” no cap, hand-editing XML is giving suffering πŸ’€. the groups-manager can load an entire file of groups metadata, then either create a new group or edit an existing group, and then write all of the groups metadata back out. πŸ¦‹

🧚 ARGUMENTS 🧚

  • <package-name-spec> β€” the package to add to a group or remove from a group. that's the vibe. πŸ’…

πŸ‘‘ OPTIONS πŸ‘‘

all general DNF options are accepted β€” see Options in dnf(8) for details. and here are the options this plugin documents:

  • --load=<path_to_comps.xml> β€” load the groups metadata information from the specified file before performing any operations. if you specify this option multiple times, metadata from all files is merged together. 🫢
  • --save=<path_to_comps.xml> β€” save the result to this file. you can specify the name of a file you are loading from, because the data will only be saved when all the operations have been performed. this option can also be specified multiple times. ✨
  • --merge=<path_to_comps.xml> β€” this is the same as loading and saving a file, however the "merge" file is loaded before any others and saved last. main character ordering honestly. πŸ‘‘
  • --print β€” also print the result to stdout. for the girlies who like to see it. πŸ’…
  • --id=<id> β€” the id to lookup/use for the group. if you don't specify an <id>, but do specify a name that doesn't refer to an existing group, then an id for the group is generated based on the name. πŸŽ€
  • -n <name>, --name=<name> β€” the name to lookup/use for the group. if you specify an existing group id, then the group with that id will have its name changed to this value. 🫢
  • --description=<description> β€” the description to use for the group. ✍️
  • --display-order=<display_order> β€” change the integer which controls the order groups are presented in, for example in dnf grouplist. πŸ”’
  • --translated-name=<lang:text> β€” a translation of the group name in the given language. the syntax is lang:text. eg. en:my-group-name-in-english. 🌈
  • --translated-description=<lang:text> β€” a translation of the group description in the given language. the syntax is lang:text. eg. en:my-group-description-in-english. πŸ’œ
  • --user-visible β€” make the group visible in dnf grouplist (this is the default). default slay. ⭐
  • --not-user-visible β€” make the group not visible in dnf grouplist. incognito mode. πŸ™ˆ
  • --mandatory β€” store the package names specified within the mandatory section of the specified group; the default is to use the default section. 🫢
  • --optional β€” store the package names specified within the optional section of the specified group; the default is to use the default section. 🌸
  • --remove β€” instead of adding packages, remove them. note that the packages are removed from all sections (default, mandatory and optional). no hiding. πŸ’€
  • --dependencies β€” also include the names of the direct dependencies for each package specified. πŸ”₯

πŸ’Œ AUTHOR πŸ’Œ

see AUTHORS in your Core DNF Plugins distribution. 🫢

2026, Red Hat, Licensed under GPLv2+


okay that's the whole page, bestie. πŸ’– this was dnf-plugins-core, version 4.7.0, dated Aug 10, 2026. now go make some groups metadata and slay. πŸ¦‹βœ¨

πŸ“¦ where this page comes from