Per-Product Config file divergence

Toshio Kuratomi a.badger at gmail.com
Mon Mar 10 17:09:43 UTC 2014


On Mon, Mar 10, 2014 at 10:40:29AM -0600, Chris Murphy wrote:
> 
> On Mar 10, 2014, at 10:10 AM, Toshio Kuratomi <a.badger at gmail.com> wrote:
> 
> > At last week's FESCo meeting, the fact that Products desired to have
> > divergent configuration was briefly touched on.  On Thursday, a few FPC
> > members had a brainstorming session about it and on Friday, sgallagh and
> > that brainstorming continued with sgallagh, adamw, tflink, notting, and
> > myself.  We came up with a tentative idea here:
> > 
> > https://fedoraproject.org/wiki/User:Toshio/Product_Divergence_(config)
> > 
> > The idea is to allow config file divergence via the alternatives system as
> > that already provides us with a commandline tool and some structure to build
> > on.  We'd still have to write a few pieces to complete the picture but it
> > seemed to be a better starting point than using rpm Conflicts between
> > config-packages.
> > 
> > Anyone have thoughts on this potential path?
> 
> What will fedup updates of Fedora 20 look like? Would there be a flag, e.g. --product cloud/workstation/server? If not specified do we fail, or is there a default?
> 
> Or is this getting too far ahead of things?
> 
The default should be whatever product was installed onto the system
originally.  Going from Fedora 20 to a Product in F21 is probably a one-off
but I'm not sure what that should look like.  I could be totally wrong but
I believe that each of the Products will have their own install image.  With
that in mind, fedup might need a one-off bit of UI to ask which Product
image you want to use.  That image would then set the Product on the disk
accordingly.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140310/7960b2bb/attachment-0001.sig>


More information about the devel mailing list