DNF4-GROUPS-MANAGER(8)
β¨ 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 indnf grouplist. π’--translated-name=<lang:text>β a translation of the group name in the given language. the syntax islang:text. eg.en:my-group-name-in-english. π--translated-description=<lang:text>β a translation of the group description in the given language. the syntax islang:text. eg.en:my-group-description-in-english. π--user-visibleβ make the group visible indnf grouplist(this is the default). default slay. β--not-user-visibleβ make the group not visible indnf 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. π«Ά
π COPYRIGHT π
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
- centos-stream 10: dnf-plugins-core 4.7.0-12.el10 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms