On Sat, 05 Feb 2000, Guy T. Rice wrote in an email to me:
> > The input of networking information is too late, since networking
> > characteristics influence the selection of RPMs to install.
>
> I hope not. My network card can't be detected during install (requires ISA
> PnP tools and a config file). I can't answer yes to networking since it
> then attempts to configure things it can't. I need to answer no here, then
> set things up manually later. If it then fails to install RPMs I need for
> networking because I said "No" to _configure_ my network during install,
> this would be highly annoying. What RPMs are installed or not should depend
> on my installation class.
Installation class is one thing. Networking is another distinct
orthogonal thing, since all classes may or may not be networking (except
server, where a networking assumption may be valid). Both these
orthogonal attributes affect the choice of RPMs.
> What I _configure_ during installation is a
> seperate issue entirely, and _should not affect_ what is installed.
The end product of an installation process is an immediately usable product,
surely? Therefore configuration for a specific usage is properly an
intrinsic part of installation (though IMO it must be pre-scriptable (and
post-scriptable) so the same installation can be repeated any number of
times without reinputting the decisions).
--
Regards,
Ron. [AU] - sent by Linux.
