You are viewing illiterat

James Antill - Understanding groups in yum

Aug. 7th, 2008

11:40 pm - Understanding groups in yum

Previous Entry Add to Memories Share Next Entry

Comments:

From:cwickert.id.fedoraproject.org
Date:January 23rd, 2010 10:23 am (UTC)

Even bigger problem...

(Link)
The biggest problem I see with yum and groups is the way how yum determines if a group is installed or not: Ether all mandatory packages need to be installed or - if there are no mandatory packages in that group - at least one optional package. It's hard to follow this logic and impossible to visualize this in a UI. This means that it's impossible to install a group with gnome-packagekit because it is already shown as installed.

Say I just have the core components (mandatory packages) of a group installed and want to get the default package selection I would get with yum groupinstall. How would I do this graphically? Impossible!
[User Picture]
From:illiterat
Date:January 25th, 2010 05:36 pm (UTC)

Re: Even bigger problem...

(Link)
I assume you are talking about gpk-applications's "package collections" UI. But that's not yum's problem, IMO. The problem there is PK designing the UI for the LCD, which is group == single fixed collection of packages ... which isn't what the word "group" has ever meant to yum or Fedora and I seriously doubt it's what any user wants.

The newer gpk-app's also have the real groups UI on Fedora, and that's much better (giving you a browsable tree) ... but it still doesn't map very well to what Fedora/yum provide, and again I have a hard time blaming anything but PK for that failed mapping.

I also don't see how the yum side could make PK's life easier, even if we implemented some of the proposals to make groups "easier" (like making groups real objects, so they update etc.) ... that would require even more work on the PK side to represent that. About the only thing we could do is regress groups to the state of meta-packages, which is what Debian/Ubuntu uses.