Per-Product Config file divergence

[Stephen Gallagher]

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

On 03/10/2014 03:25 PM, Gabriel Ramirez wrote:
> On 03/10/2014 12:44 PM, Stephen Gallagher wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> 
>> I'd rather see us handle things this way:
>> 
>> fedora-release Requires: fedora-release-variant
>> 
>> fedora-release-$PRODUCT[1] Provides: fedora-release-variant
>> 
>> The first fedora-release-$PRODUCT package installed on the system
>> sets the base product/spin appropriately (in some well-known
>> config file, not necessarily /etc/os-release)
> but what happens with the people using kickstarts to install
> Fedora, by example I'm using kickstarts to install the following
> 
> - @core @standard groups and 5 to 10 specific rpms (bind,
> lighttpd, postfix) - @core @base-x @virtualization and a list of
> 300 rpms packages
> 
> so will be required to install a product (fedora-release-variant)
> and by consequence  add more rpms to my kickstarts installs?
> 


You misunderstand. This is "if a package requires a choice, it will
provide a default and this can be explicitly changed by passing
- --product=something". If you DO have a Product installed, it will
treat all yum commands as including --product=something unless you
specify it otherwise.

The default case (if no Product is installed) must be addressed.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMeFZYACgkQeiVVYja6o6OAaACeKzp7DKK5YgxqWFf7smOnDKri
zR4AoKcRixEIvliUM17pMA0UBtEqSxX6
=JWAR
-----END PGP SIGNATURE-----