-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/10/2014 02:09 PM, Matthew Miller wrote:
> On Mon, Mar 10, 2014 at 10:09:43AM -0700, Toshio Kuratomi 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?
>> 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.
>
> I assume that we'll do something that makes it easy to read the
> existing product from the system -- I like fedora-release +
> fedora-release-{workstation,server,cloud} subpackages.
>
> And I think those subpackages probably _should_ conflict, don't
> you?
I would actually think that (so far as possible) we should be able to
make them capable of not conflicting.
I'd rather see us handle things this way:
fedora-release Requires: fedora-release-variant
fedora-release-$PRODUCT[1] Provides: fedora-release-variant
The first fedora-release-$PRODUCT package installed on the system sets
the base product/spin appropriately (in some well-known config file,
not necessarily /etc/os-release)
Other fedora-release-$PRODUCT packages can be installed later for the
purposes of pulling in their packages. By default, unless
- --product=$NEWPRODUCT is passed to yum, any packages they pulled in
would get the original product's alternative default config provided
(if there is one; we also need to design this mechanism so that the
assumption is that there is no difference unless specified)
My reasoning is that I think it should be easy to turn a Fedora Cloud
deployment into a Fedora Server simply with 'yum install
- --product=server fedora-release-server' and similarly that I should
potentially be able to install a graphical environment for Fedora
Server by doing 'yum install fedora-release-server-graphical'[2][3].
[1] Where $PRODUCT might be a spin identifier
[2] Where fedora-release-server-graphical might be equivalent to
fedora-release-workstation or might be a different set, depending on
how we decide to cultivate it.
[3] This particular case is weak, as if it's *not* Workstation
equivalent, we'd be more likely to treat it as a simple yum group,
since it's unlikely to need separate default configuration from the
Server.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlMeCCEACgkQeiVVYja6o6O05gCePlScDpjTGExA3ruvUoseTo1L
8ZMAoJgZ6h8sAxRxJOlAKoVf1/GSLh/E
=L6EH
-----END PGP SIGNATURE-----
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
