johan...@sun.com wrote:
I think you have this backwards. If a package comes from /contrib and
its dependencies aren't satisfied, you can't install it and break your
system. You're asking for the --no-deps option so you can install the
broken package and have who knows what happen to your system.
Yes, that's exactly what I want.
If a package is broken in a first place even installing it with all its
dependencies no-one knows what will happen to your system - so still the
same situation.
But if I know (at least I think) what I'm doing then I can do it a hard
way (by publishing an altered manifest) or I can just do rpm --nodeps
... and end up with the same result... or maybe even worse as I might
have never played with spec files, etc. and could end up even in a worse
situation.
People won't use --nodeps by default only under some situations when it
is required.
--
Robert Milkowski
http://milek.blogspot.com
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
