Re: Per-Product Config file divergence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

thanks,

Gabrielo
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux