New Zealand (South Island)
Seth Kenlon is a UNIX geek, free culture advocate, independent multimedia artist, and D&D nerd. He has worked in the film and computing industry, often at the same time. He is one of the maintainers of the Slackware-based multimedia production project Slackermedia.
Authored Comments
I don't understand the question, because 3 commands are not needed. I believe this article demonstrates that effectively.
The 3 commands you list do, however, exist. I can provide some context:
* Yum is historical, and has been refactored to be based on libdnf. It's now an optional interface to dnf for people who have enjoyed Yum over the years and don't want to migrate away from it. It wouldn't surprise me if it eventually is deprecated or symlinked to the `dnf` executable.
* The `rpm` command is a direct interface to the RPM database tracking packages on the system. It exists because Linux provides the user with lots of tools, and it would be a pity to put a database on a user's system with no way to communicate with it. Generally you shouldn't expect to use the `rpm` command, because dnf is a friendlier, unified, and robust way to interact with the RPM system.
I do a grouplist with the -v flag, which lists the exact group nickname in parentheses.
$ dnf grouplist -v
RPM Development Tools (rpm-development-tools)
Development Tools (development)
Graphical Administration Tools (graphical-admin-tools)
$ sudo dnf install @development
There may be other ways to do it, but that's what I've done for years-n-years and it hasn't let me down so far.