[CentOS-devel] Centos server installation

Les Mikesell lesmikesell at gmail.com
Tue Aug 2 12:01:19 EDT 2011


On 8/2/2011 10:28 AM, 夜神 岩男 wrote:
>
>> I am assuming that he means to suggest a button to "select all" in a group.
>> Right now on certain groups when you select them for installation will
>> only install for example 11/93,
>> I think he means to add a button that allows him to add the other 82 in
>> a single click.
>
> We had this discussion in Fedora-land a while back. There are pretty
> solid reasons why this was removed in Fedora and later RHEL as an option
> (the FESCo logs of it are around somewhere, as are a few blogs detailing
> this after the fact).
>
> Installing *everything* is not normal use and can cause weird things to
> happen (depending on use -- for example when alternatives install next
> to or over defaults and admins often don't realize this is happening,
> particularly with sendmail/postfix or 389-DS/OpenLDAP).

It would be nice if someone who chose the available packages and has at 
least some understanding of them would also provide an 'everything' 
choice that is a set of all the package that won't cause weird things to 
happen.  Disk space is cheap and it is much easier to explore/test 
programs when they are installed than by reading the itty-bitty blurb 
that 'yum info' gives.  Was there anyone in the fedora-land discussion 
who thought an end user would really be able to select packages 
sight-unseen better than the people who made the choice of packages to 
be included in the distro?

> ...and for people who *really* want to do this, 'yum install"*"' works
> just fine and lets you know a lot more than Anaconda does. The quotes
> around the * are necessary. This can be placed in a kickstart script or
> a firstrun hack but neither tier of upstream consider it a good idea to
> tempt the average person installing a system with such a nuclear option
> before they've even seen the system defaults working the way they were
> designed...
>
> Anyway, wouldn't this break "binary compatibility with upstream"?

Agreed - it is something that upstream should provide too.  Or at least 
a yum group or list of packages in a form that yum would understand to 
install them later.

-- 
   Les Mikesell
    lesmikesell at gmail.com


More information about the CentOS-devel mailing list