On Fri, 2014-06-27 at 12:36 +0200, Stef Walter wrote:
So this may be obvious to some of you, but how do we handle the case
where installed files need to be different between Fedora Server and
other Fedora flavors?
For example for Cockpit to be installed by default we need to:
* Add the cockpit service to all relevant zone files in
/usr/lib/firewalld/zones (currently owned by firewalld rpm).
See 'man firewalld.zone' and 'man firewalld.service'
* /etc/pam/sshd needs an addition module, for Cockpit reauthorize to
work with added servers. See:
... and likely others.
So I guess the question is how do we adapt behavior of rpms that are
installed both on Fedora Server *and* on other Fedora flavors.
So these are basically all configuration items, I can see two ways to go
1. in the .spec file we have a flavor based conditional that runs
scriplet only if the install target is of the right flavor.
This has the problem that if we allow switching flavor after install I
am not sure there is a way to run the conditional scriplets easily.
yum reinstalling a package after the switch can be considered a
reasonable workaround for F21 ?
2. Drop configuration scripts in some per-flavor area, and have a way to
run these after first-boot or via a yum/dnf plugin that runs at the end
of a transaction ?
This looks more flexible but would also require more infrastructure we
do not have at the moment.
Follow up question: How would I install Fedora Server today? What
where are the diffs from the usual Fedora Rawhide represented? Is Fedora
Server still a completely theoretical construct at this point?
I do not think we have anything on the ground yet, but we should
certainly start working on it.
Simo Sorce * Red Hat, Inc * New York