On Sun, 2014-12-14 at 13:34 +0100, Richard Z wrote:
On Sun, Dec 14, 2014 at 12:06:05PM +0000, Patrick O'Callaghan
wrote:
> On Sat, 2014-12-13 at 19:38 -0600, Glenn Holmer wrote:
> > On 12/13/2014 10:32 AM, Matthew Miller wrote:
> > > Naming things is famously hard; I agree — we could to better here. Any
> > > suggestions? I would also like to find better way to distinguish the
> > > spins like KDE desktop, where there is full QA and a number of
> > > dedicated people, from those which get minimal effort and often have
> > > serious problems that no one fixes.
> >
> > Fedora Workstation with GNOME
> > Fedora Server
> > Fedora Cloud
> >
> > alternate workstation versions (supported):
> > Fedora Workstation with KDE Plasma
> > Fedora Workstation with Some Other DE
> >
> > alternate workstation versions (unsupported):
> > Fedora Workstation with Some Wonky DE
> > Fedora Workstation with Some Other Wonky DE
> >
> > 1) important to note that the default workstation includes GNOME
> > 2) hoping "supported" doesn't imply too much
> >
>
> I could live with that as a description. However part of the question at
> issue is what invocations of fedup should exist to get the result the
> user wants, so a more compact form is needed. That's why I proposed a
> way of doing that earlier in the thread.
do we really need any of it for fedup? I would think people use fedup to
upgrade, not to switch to a different product.
If that were true, we wouldn't need any options and fedup would just
upgrade whatever the user already had.
Why would a gnome user want to type "fedup
--product=workstation" instead
of "fedup --product=nonproduct" - other than because of the misleading
commandline options?
Sorry, can't parse what you're getting at here.
Similar for KDE users if there would be product=KDE ?
Part of my objection is simply to the term "product", which I think is
unfortunate. I was pushing "model" as slightly better.
poc