Hello, here are some general ideas I have for the installation proceedure.
For starters, since theres a number of absolutely required packages, the
entire lot of those could be installed while the user is selecting additional
packages.
Another thing, the current method of installation is daunting for new and
seasoned users, simply because of the sheer glut of packages to choose from.
I would rather like to have the installer ask a few dozen questions about my
useage, and the computers role, then present a list of packages that pertain
to my answer for each question.
Heres some suggested ones..
X windowing system [yes no]
if no: X applications [yes no]
(this would give you the ability to either have X, or not have X but still
have X applications (for use on a remote X display), or no X apps at all)
Multiple language support [yes no]
Cd authoring software [yes no]
Sound [yes no]
Local Area Networking [yes no]
Dialup Networking [yes no]
graphics manipulation [yes no]
graphics viewing [yes no]
motion video [yes no]
etc etc..
btw, there are times when i want a mandrake box that doesnt have any X stuff
on it!
The general idea here is to axe large swaths of packages that the user wont
ever need. As well, it will help to show the user what packages they really
do want. The problem with the current way of doing it is that the user
doesnt know what each package does, so the user may accidentally install
something that isnt really needed, or deslect something that actually is
needed. This alternate way of doing things should also speed up the
selection process.
Another <crackpot=on> idea is rpm meta-packaging. ie, have an empty rpm
which just has masses of dependencies to other packages.
examples:
c-development.meta.rpm
kde-desktop.meta.rpm
gnome-office.meta.rpm
cd-burning-tools.meta.rpm
games-arcade.meta.rpm
it would make removal of software easier too.. the kde|gnome fanatics would
love this feature. hehe (rpm -e gnome-desktop kde-desktop Ahhh)
If you were handed a workstation that was missing some stuff that you needed
(c development perhaps) then you could grab one of these meta packages, and
have it install everything related to it. It would beat the hell out of
manually comparing the cooker RPMS list to 'rpm -q foo' several thousand
times.
Any thoughts?
Jason
