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.
Kevin Kofler
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
