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

Stephen Gallagher sgallagh at redhat.com
Thu Jul 3 13:57:06 UTC 2014


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

On 07/03/2014 01:42 AM, William wrote:
> On Wed, 2014-07-02 at 20:40 -0700, Samuel Sieb wrote:
>> On 07/02/2014 06:55 PM, William wrote:
>>> 
>>>> 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).
>>> 
>>> How will this work with fedup from 20 to 21? Will there be
>>> multiple upgrade targets?
>>> 
>> Why would that be necessary?  All packages are in one repository,
>> so fedora-release-$PRODUCT will be upgraded to the next version
>> and everything will be fine.
> 
> My machine doesn't currently have a fedora-release-$PRODUCT
> package installed. So how will fedup work out what one to put on my
> system? Will these packages be added to 20, and the user need to
> preinstall before fedup?
> 

It won't put one on your system. Upgrades from a non-Productized
Fedora will remain non-Productized. It's not *less* Fedora than before.

The Products are basically a statement that "this minimal set of
packages and services are available on the system". A non-productized
Fedora install is essentially just a continuation of the classic
do-it-yourself approach that Fedora has been up to this point.

I hope that clarifies things for you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlO1YTIACgkQeiVVYja6o6OKuwCgsetv/Dr3umWKlCLvgEeqIJat
i30An3NCXXVeYe6K5iEYhEWe1yPjhor0
=mBtM
-----END PGP SIGNATURE-----


More information about the devel mailing list