> >>Likewise, if you click ash off, up pops a window listing everything > >>that depends on ash, with an addiotnal message of "Warning: removing > >>ash will cause these packages to be removed as well. > >> > > > >This does make quite a bit of sense to me. But wouldn't MessageBox() > >or something akin to it be a better fit to the task? The only possible > >user input here would be "Yes, remove ash and everything dependent on > >it" and "Cancel", and the only output a list of package names. > > Actually, I think that automatically removing dependencies is not a good > idea. If I select binutils specifically, then select gcc, then uninstall > gcc, I would probably be annoyed to see binutils disappear. > > cgf
I took it to mean the opposite - if you uninstalled *binutils*, it would uninstall gcc because gcc depends on them. But on further reflection I'm no longer sure even that is desirable. If I uninstall ash, should say make get deleted even though I have bash as sh? -- Gary R. Van Sickle Brewer. Patriot.