Is there an ‘after the fact’ way to find what yum groups are installed, including ones that were added with ‘yum groupinstall’
instead of the initial anaconda install?
Yes. “yum grouplist” will tell you the groups that are currently in the installed state. Worth reading the manpage to see exactly what yum thinks that “installed” means:
Groups are marked as “installed” if all mandatory packages are
installed, or if a group doesn’t have any mandatory packages then
it is installed if any of the optional or default package are
Fedora Project Leader
But, I think that is a YUM database and not based on the RPM database, so it is possible that you can have all the RPMs for a group installed and not actually have it listed as installed.
At least I sometimes find myself in that position. But I also wipe out
Interesting, but it seems to _only_ show groups that weren’t included in the anaconda install. For example where the saved anaconda-ks-cfg shows @gnome-desktop and @development, ‘yum grouplist’ only shows
‘MATE Desktop’ which was installed later.
What I am looking for is a succinct way to duplicate the full installed package list that exists on an organically-developed developed system (that is, where people added things until it all worked), so equivalent systems can be created by a minimal install followed by a scripted yum install ‘big list of stuff’.
I think the info of “what’s in a group” comes from the yum cache, but yum uses the actual state of the system (the rpm database) for what’s installed.
That’s what I think. I guess we could look. :)
Does the “hidden” flag help here?
Well it’s different, but still doesn’t seem right. That shows:
Installed environment groups:
MATE Desktop and Installed groups:
Dial-up Networking Support
Guest Desktop Agents
Multimedia but still no mention of development or gnome.
And I guess the other piece of this would be finding individual packages that are not encompassed by the groups – or pulled in by dependencies. Is there some database-like approach to take the full list of packages, then reduce it to the minimal list of groups and top-level packages to pull the rest in? It probably will work to hand the raw list to yum but I’d like to make an understandable list in a script even if the packages had been added piecemeal in the first place as someone noticed the need for them.