Hello,

I am from the Anaconda installer team.

There is an effort to get rid of fedora-productimg-[server,workstation,cloud,atomic] packages [1].
The packages used to contain two product-specific additions to installer environment:

1) The product-specific installclass (python file) for anaconda installer. We are moving it into anaconda source tree [2].

2) The product-specific look of the installer GUI.
Basically, a .css file referring the images/logos from fedora-logos package. The productimg package installs the .css and creates symlinks to appropriate icons from fedora-logos (eg /usr/share/anaconda/pixmaps/server subfolder). If we referred the icon files directly from the .css (instead of using symlinks created by productimg package) file and moved the .css file to some other package we could get rid of the productimg package completely.

The question is where the .css file should be packaged. Given it refers product-specific image files from fedora-logos, one option would be to have product-specific .css files included in the fedora-logos package as well (installed to /usr/share/anaconda/fedora-server.css). Would it make sense from your POV? Or do you know about any more-suitable package?

Thank you,

Radek

[1] https://github.com/rhinstaller/anaconda/pull/1249
[2] so they can be maintained and adapted to changes in installer more easily. There is no formal API for installclasses defined so changes in anaconda sometimes result in installclasses not being updated accordingly. Moving the installclasses into the tree should make this better and also would allow us to adapt the installclasses to longer term general changes where we would like to make them use more stable and actually specified API for installclassses.