Red Hat Bugzilla – Bug 187108
pirut groups view should show mandatory packages
Last modified: 2008-05-06 11:41:00 EDT
in groups view, pirut currently doesn't show mandatory packages
This is confusing - for example, let's say I want to install an ftp server. I go
to Servers, then enable "FTP Servers". There's no indication displayed anywhere
that I'm getting vsftpd automatically, so I'm likely going to go ahead and
install proftpd or pureftpd under optional packages because it looks like I'm
not getting anything otherwise
Better design, I think, would be something like changing "Optional Packages" to
say something like "Detailed View". When you select "Detailed View", it shows
you the mandatory packages (with no option to deselect) and then below them the
optional packages, with the option to select or not as you see fit
So, I continue to go back and forth about this. You've covered one side of the
The other side is that showing the mandatory packages won't necessarily show the
full view. eg, it doesn't do dependency resolution so you won't realize when
packages are pulled in by deps. But maybe the answer there is that if it's an
"interesting" package, it should be included as mandatory even if it is going to
get pulled in by a dep anyway.
I can probably be swayed either way. Maybe it'll just be something that changes
from one to the other each release ;)
Agreed that showing the mandatory still doesn't give a complete picture, but it
does give a more usable one
Think again about the usage case I gave -- trying to install an ftp server. Do I
care that when it selects vsftpd as mandatory that later when it does dependency
resolution it'll also select logrotate? It's nice to know, but I don't really
care in the same way that I do need to know that if I select the FTP Servers
I've already implicitly selected vsftpd, and therefore don't also need to select
I can't really think of a usage case why anyone would prefer the current
Stumbled across this --- need to check it and either fix it or close it.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.