On Mon, 2006-03-06 at 15:38 -0600, Les Mikesell wrote: > On Mon, 2006-03-06 at 13:37, Andy Green wrote: > > > >>> machine with 'everything' installed, how are you supposed to > > >>> find out what is available and if you like it? > > >> Lots of packages can be installed and not really discoverable from the > > >> system menus. If a commandline utility goes in /usr/bin then unless you > > >> know the name you will likely never be aware of it (I guess apropos > > >> might help). So "install everything" so I can try things is really > > >> "bloat me" with many things I will never know I have. > > > > > > OK, how do you try out those things? If you are content with > > > the packages from years ago, why install a new system at all? > > > > Sorry I didn't understand how that applied to what I said. For the > > record I like new stuff that is better than the old stuff. My point was > > that "install everything" is not the same as "discover everything". > > OK, then explain the process of discovering everything without > installing it first. That might save me a lot of time. I don't > remember saying anything about menus, though - how do you find > the new command line programs when they and their corresponding > man pages aren't installed? > And you think that the "everything install" provides man pages and menu options for all that is installed. Or that everything installed is actually documented in detail for the user. Please wake up to reality! > -- > Les Mikesell > lesmikesell@xxxxxxxxx > >
