On Mon, 15 Mar 2010, Adam Williamson wrote:
> On Mon, 2010-03-15 at 09:50 -1000, David Cantrell wrote:
>
> > The names of the tasks maybe need more description. The reason
> > they are radio buttons instead of checkboxes is that the choices
> > indicate preset lists of yum package groups to install.
>
> I may be dim, but why does that mean they have to be radio buttons?
> Can't anaconda just sum the list of package groups if you pick more
> than one option? I don't see any intrinsic reason why the user
> _shouldn't_ be allowed to configure a system that's both a Graphical
> Desktop and a Software Development system, say.
i was about to make precisely the same observation -- i don't know a
single person amongst my linux social circle that would install a
system that didn't incorporate the graphical desktop *and* the
standard S/W development tools.
and, yes, i *realize* that one can always pop into customization to
set it up exactly the way you want, but the whole point of those
initial radio boxes is, i assume, to give people a quick way to pick a
configuration, but that doesn't do much good if the only
configurations you support are combinations that most people wouldn't
select in the first place.
i suppose one could put in a BZ request but i can't imagine that
would have much effect since that really would constitute a major
change in functionality.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
