RE: cleaning up our task packages

["Josh Miller" <joshlists@nebonet.com>]

Something like:

Internet
-Browsers
--lynx (default)
--Mozilla (which would select K or gnome or whatever the default is)
--...
-MUAs
--mailx (default)
--mutt
--...
-IRC Clients
--BX (default)
--IRCII
--...
-...
Programming Environment
-C (default)
-C++
-Fortran
-Python
-...
Servers
-Database
--PostgreSQL (default)
--MySQL
--...
-E-Mail
--(Whatever these are)
---IMAP (default)
---POP3
---...
--MTAs
---sendmail
---exim (default)
---...
--Miscellaneous
---procmail
---vacation
---...
--...
-...
...

Of course, this makes it more like dselect or such, although easier to find
things in the same category...

And to be able to sort like this, task packages might need to be created
differently to contain all the necessary information...

And I just pulled those defaults out of the air ;)

-
Josh


Andrew McMillan wrote:

>...
> The idea of having tasks within tasks that someone suggested seems a
> good one though. If you could have a structure of tasks then you could
> have a top level task which selected (by default) the lower level ones,
> but still allowed override of lower level tasks.
>
> For example, you list "Database Pg" as one task.  Much as I am a fan of
> PostgreSQL there are other choices, so it should really be "Database
> Server", and it should default to being a PostgreSQL database server.
> The interface (blithely ignoring implementation details here!) could
> allow the user to track into "Details" and adjust things for different
> defaults.
>...