[Base] Fedora Base Design Working Group (2014-07-11) meeting minutes and logs

[Mike Pinkerton]

On 25 Jul 2014, at 07:52, Phil Knirsch wrote:

> Summary:
>
> Mattdm then followed with 2 1/2 additional topics:
>
> 1a. Identifying different Fedora products -- fedora-release-*  
> contents and /etc/os-release

As I understand it, you are trying to decide where and how to set a  
flag that will signal the "product" that is either installed or to be  
installed.  There was mention of dropping "product specific snippets  
in /usr/lib/os-release.d/" as one solution.

Does it have to be any more complex than the approach used by  
systemd?  If fedora-release were to drop all product specific  
snippets in /usr/lib/os-release.d/, then a system admin could use a  
symbolic link in /etc/os-release.d to flag which product (or no  
product) he wanted installed.  Similar to:

/etc/systemd/system/default.target -> /lib/systemd/system/ 
graphical.target

a system admin could set a symbolic link:

/etc/os-release.d/product -> /usr/lib/os-release.d/workstation.product

Then, if a system admin wanted to change the box to a server, or to a  
non-productized box, he could simply change the symbolic link to:

/etc/os-release.d/product -> /usr/lib/os-release.d/server.product

or

/etc/os-release.d/product -> /usr/lib/os-release.d/generic.product

and then run whatever product syncing tool you develop -- perhaps:

dnf product-sync

> 2. a "generic fedora" netinstall

I appreciate your continued consideration of this item.  I'm not  
clear on how Anaconda is supposed to work with different products,  
but if it is reading whatever product flag you set in order to  
determine the package list, couldn't a single netinstall CD work for  
all products, as well as a generic, non-productized install, assuming  
that there were a place in the UI to specify which product the user  
wanted installed?

-- 
Mike Pinkerton