On Fri, Oct 17, 2008 at 12:00:17AM -0700, Jordan Brown wrote: > Bart Smaalders wrote: >> For example, install SUNgcc... now install gcc-dev, which included >> SUNWgcc. Should uninstall of gcc-dev remove SUNWgcc? >> >> >> Absent a brainstorm on how this should work, we've put off dealing >> with this :-). > > It's a headache with no good answer that I've come up with. I have the > same problem with a traditional installer that brings along components that > might be shared, that might have already been present. > > So far the best answer I've got is "delete everything you might have > brought along, whether or not you installed it, as long as nobody else has > declared a dependency on it". That's not awful for middleware, but it's > wrong for anything the user might interact with directly.
As Bart mentioned, we've been tossing around the idea of intent -- not the server-side intent that Shawn's implemented, but a client-side form of it. We'd keep track of why any given package got installed -- was it something the user specifically asked to be installed via pkg install, or by clicking on it in the gui, or was it dragged in by some dependency. Thus we would be able to determine how to recursively uninstall non-leaf packages by only doing so if they were never intentionally installed, and no remaining packages had dependencies on them. Of course, that requires more plumbing than we currently have, but it might be a way forward on this problem. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
