fedora-release-$PRODUCT, /etc/issue, /etc/os-release, Per-Product Configs and more!

Stephen Gallagher sgallagh at redhat.com
Mon Jun 30 18:59:20 UTC 2014

Hash: SHA1

We're getting down to the wire on Fedora 21 and we need to nail down a
few of the low-level release requirements.

First of all, I'd like to formally propose that each of the products
will have a fedora-release-$PRODUCT (and corresponding
generic-release-$PRODUCT) package. This package will meet several
needs (with magical hand-waving in this initial email).

1) All Products will add explicit Requires: to the
fedora-release-$PRODUCT package so that they may define their minimal
operating set properly. The presence or absence of this package on the
system will indicate definitively which Product (if any) is operating

2) The fedora-release-$PRODUCT package (and possibly %post or systemd
snippets therein) will be responsible for the creation and maintenance
of /etc/issue, /etc/os-release and /etc/fedora-release-product (note:
there is no $ there. That's the literal name. This file will be
equivalent to /etc/fedora-release except that it will include the
Product name.

3) fedora-release-$PRODUCT will have an explicit Conflict with all
other fedora-release-$PRODUCT packages, to ensure that we do not
mix-and-match (which is a combinatorial nightmare).

Additionally, I am working on a proposal[1] for per-product configs in
the Fedora 21 timeframe which is dependent on the above. It should be
noted that this is an interim solution only; in Fedora 22 we will be
able to vastly simplify this situation with the weak dependency
support in RPM 4.12. (I was looking for a link detailing all of these
weak deps, but I cannot find one. If you know of such a document,
please reply and add it).

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


More information about the devel mailing list