Next big activity is pushing the required CentOS 8 packages to the Uyuni Master branches.
The distribution of packages to repositories on the Uyuni Server are:
- Uyuni Master: 98 + Uyuni Master Other: 58
- New custom packages: 46
- EPEL: 34
- PowerTools: 50
- CentOS 8 BaseOS: 477 + CentOS 8 AppStream: 196
1) I would push my newly created custom packages including kits to "Uyuni Master
Other". Are there any guidelines? Otherwise I would just split out the change log of
the spec file and submit.
2) What do we do about the EPEL and PowerTools packages? I feel a bit uneasy of pushing 84
packages (+ probable build dependencies) to OPS. Especially when you consider that these
packages need to be maintained and monitored for security fixes.
3) One more (not so pleasant) thought is the module system. Installation requires
activation of 10 modules and deactivation of 2 more modules. If we go for loading all
packages of point 2) into OBS, we might as well add the ones from the modules and create
an Uyuni Server module (one per major release?). That would simplify the user experience
and probably use the module system as intended (but kill maintainability...).
Let me know your thoughts and ways to continue.