Per-Product Config file divergence

[Stephen Gallagher]

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

On 03/10/2014 03:58 PM, drago01 wrote:
> On Mon, Mar 10, 2014 at 6:22 PM, Kevin Fenzi <kevin at scrye.com>
> wrote:
>> On Mon, 10 Mar 2014 10:09:43 -0700 Toshio Kuratomi
>> <a.badger at gmail.com> wrote:
>> 
>>>> 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.
>> 
>> Or we could simply say that fedup doesn't upgrade from a non
>> product to a product. You have to re-install or use a manual
>> method to do that (some yum/dnf commands, etc).
> 
> We shouldn't make things harder for users to make it easier for us
> .. that's backwards.
> 

Yeah, we really need packages to have a "true" default (which is used
if no Product is specified) and then may have other Product-specific
defaults. In one of my other responses to this thread, I postulated a
straw-man solution for this. Feel free to bring torches :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMeG3QACgkQeiVVYja6o6MSDQCghZS7sLjBtgZ4IUK9/cT0GYmf
mJ8An0HGGYW30S4GoccOfDNiTngfb9iI
=fl2X
-----END PGP SIGNATURE-----