YUM-GROUPS-MANAGER(1)

💅 NAME 💅

ok so this is yum-groups-manager — bestie, it's literally redirecting to the DNF groups-manager Plugin. It's the page from the dnf-plugins-core manual, and what it does is create and edit groups repository metadata files. slay.

---

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

okay so picture this: the groups-manager plugin is the thing you use to create or edit a group metadata file for a repository 💖 and honestly? it's giving so much easier than writing/editing the XML by hand. no cap. The groups-manager can load an entire file of groups metadata and either create a new group or edit an existing group, and then write all of the groups metadata back out. main character energy fr fr.

---

🎀 ARGUMENTS 🎀

• <package-name-spec> — a package to add to a group, or to remove from a group. that's the whole vibe.

---

🌸 OPTIONS 🌸

so like, All general DNF options are accepted, see Options in dnf(8) for details 👑 — yeah, the whole general DNF option set is welcome here.

• --load=<path_to_comps.xml> — load the groups metadata information from the specified file before performing any operations. and if you specify this option multiple times? the metadata from all the files gets merged together. lowkey iconic.
• --save=<path_to_comps.xml> — save the result to this file. yes you can name a file you're loading from, because the data only gets saved when all the operations have been performed. also, this option can be specified multiple times. periodt.
• --merge=<path_to_comps.xml> — same as loading and saving a file, except the "merge" file is loaded before any others and saved last. it's giving first-in, last-out 💅
• --print — also print the result to stdout. so you can see it. love that for you.
• --id=<id> — the id to lookup/use for the group. and here's the tea: if you don't specify an <id>, but you do specify a name that doesn't refer to an existing group, then an id for the group gets generated based on the name. cute.
• -n <name>, --name=<name> — the name to lookup/use for the group. and if you specify an existing group id, then the group with that id has its name changed to this value. glow-up alert 🦋
• --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. order matters bestie.
• --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. and heads up, this is the default ⭐
• --not-user-visible — make the group not visible in dnf grouplist. 🙈
• --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). so like, no takebacks, be sure.
• --dependencies — also include the names of the direct dependencies for each package specified. we love a thorough queen 💜

ok real talk: --load and --save and --merge all stack — you can pass each of them more than once, and the --merge file is always loaded first and saved last. that's not me guessing, that's literally in the doc 💅

---

💖 AUTHOR 💖

See AUTHORS in your Core DNF Plugins distribution 🫶

🌈 COPYRIGHT 🌈

2014, Red Hat, Licensed under GPLv2+ 👑

---

okay bestie that's the whole page 🍓 and for the cute sign-off: this was version 4.10.1, dated Mar 28, 2025 — from the dnf-plugins-core fam, and it's yum-groups-manager(1) in the manual, so now you know 💜✨