4 ms·
Red Hat (and I imagine Fedora) has a concept a little like this: when installing the system, you can select from a list of "roles", and those roles in turn impl
by __d 8y ago
Red Hat (and I imagine Fedora) has a concept a little like this: when installing the system, you can select from a list of "roles", and those roles in turn imply a bunch of individual packages.
But, there's not many of them, and from memory, there's really only "Desktop" and "Developer Workstation" as options like the sort you're proposing.
- nineteen999 8y agoRedhat/Fedora groups are broken up a lot more than that. From a RHEL 7.5 box: # yum grouplist Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager There is no installed groups file. Maybe run: yum groups mark convert (see man yum) Available Environment Groups: Minimal Install Infrastructure Server File and Print Server Basic Web Server Virtualization Host Server with GUI Available Groups: Compatibility Libraries Console Internet Tools Development Tools Graphical Administration Tools Legacy UNIX Compatibility Scientific Support Security Tools Smart Card Support System Administration Tools System Management You can install any of these later, eg. yum groupinstall "Development Tools"
- __d 8y agoSo of those, perhaps "Development Tools", "Scientific Support", and perhaps a couple of others reflect the OP's proposal of high-level task-centric modular functionality. But there's no reason that groups couldn't be configured for "Musician's Tools", "Artist's Tools", "Educator's Tools", etc.
- nineteen999 8y agoThe arbitrary groups would need to have a comps.xml file generated. https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml... You can pass these to createrepo with the -g flag to create/update package groups in an YUM/DNF repository.