#514 Question: Does the @core group contain too many packages?
Closed: Invalid by msehnout. Opened by msehnout.

Hi,

I work on the osbuild project:
https://github.com/osbuild/
It is a tool for building OS images. We define what an OS image consist of in a similar way the official kickstarts do:
https://github.com/osbuild/osbuild-composer/blob/84022a78896b59e23ed7f59f38d62a32b786e1dd/internal/distro/fedora32/distro.go#L609

If we took a cloud image as and example, in both cases (our difinition and the kickstarts) some of the packages in the @core group are removed as being either unnecessary or even harmful to some components (NetworkManager not working well with cloud-init):
https://pagure.io/fedora-kickstarts/blob/master/f/fedora-cloud-base.ks#_59
https://github.com/osbuild/osbuild-composer/issues/847
https://github.com/osbuild/osbuild-composer/issues/806

This brings me to the question: Does the @core group contain too many packages? I'd expect the @core group to be the smallest common package set in all Fedora versions. So for example in case of Fedora Cloud Base I'd expect the core group + cloud-server group to be present in the image. Or do I have a misleading expectations? e.g. core should work by itself, but in case of cloud image we need to replace some of the components found in "core" installation.

Thanks for any ideas :)


I don't think we have any formal definitions, but my understanding is that @core is supposed to be the smallest install group that contains dnf so you can install further things on it easily.

I personally would be open to reworking things, but such discussions should probibly be on the devel list.

Metadata Update from @msehnout:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Metadata