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
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?
The software says that it needs B (or C, D, E, F) to run. It is the
responsibility of the package creator to correctly state dependencies.
This is a hypothetical situation of course. Can you name a specific
usage case where you have needed to do this that wasn't a *bug* in a Sun
package?
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.
Which is exactly why we don't offer --no-deps and --force. If you
ignore dependencies and force operations, you might as well use tarballs
to install all of your software.
What's the point of using a packaging system if you're just going to
turn off all of the aspects that make it one?
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
