On Tue, Aug 25, 2009 at 2:12 PM, Darren J Moffat<[email protected]> wrote: > Peter Tribble wrote: >> >> On Tue, Aug 25, 2009 at 1:51 PM, Darren J Moffat<[email protected]> >> wrote: >>> >>> I think of two reasons why you would want to ignore dependencies: >>> >>> 1) time to install all the dependencies >>> 2) space need to install all the dependencies >>> Are there others ? >> >> 3. The dependency information is plain wrong > > That is bug so file the bug. > > Sure that doesn't help in the short term.
It sure doesn't help when the pager goes off at 3 in the morning and you're under pressure to get things fixed. >> 4. You want package A but not package B that it depends on. (Or packages >> C, D, E, F... that get pulled in.) Am I managing the system, or is the >> system >> managing me? > > Why would you want that if A really does depend on B,... ? > > Isn't this just another case of 3 ? No. The dependency information says that all the functionality of A is dependent on B. Perhaps you want just some of the functionality of A that doesn't depend on B. Perhaps you want something else. (Simply fragmenting the system into an infinite number of packages neither solves the problem nor makes it more manageable, btw.) >> 5. The dependency graph become so dense and knotted that it's impossible >> to make any changes. And, yes, I've seen this several times. > > I don't really understand what you mean by that. Ever managed IRIX? It's possible to end up in a situation where dependency requirements are such that it's impossible to make changes. You can go neither forward nor back. You could correctly argue that that's a bug, but that's no comfort when your only recourse is to reformat the system and start over. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
