Per-Product Config file divergence

Mon Mar 17 12:11:11 UTC 2014

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/16/2014 01:13 AM, Kevin Kofler wrote:
> Stephen Gallagher wrote:
>> The primary problem is that we need to be able to address the 
>> potential for packages that *aren't* part of the default install
>> to handle differing config based on the Product upon which it is
>> being installed.
>> 
>> For example, let's say that theoretically, Fedora Cloud doesn't 
>> install very many packages at all. Normal operation would be to
>> pick and choose other packages from the repos later. We need a
>> mechanism that says "if I yum install this package onto Fedora
>> Cloud, I should get a default that's sensible for Fedora Cloud,
>> which might or might not be the same as is sensible for other
>> Products".
> 
> If you know about the package at GA release time, you could still
> drop the required config file from the live kickstart.
> 

That really wouldn't scale. While I hope the set of divergent packages
would be very small, it could still in theory mean a lot of additional
wasted space if we included every possible divergent config on the system.

Moreover, we need to account for the possibility that any package
could spontaneously decide that it should have a different default for
one Product than another. We need to be able to adapt to that post-GA.