Robert Milkowski wrote:
Darren J Moffat wrote:
Other than the "broken dependencies" issue why else would you want to
skip dependencies ?
From my experience --nodeps or --force is mostly useful on system where
for some reason a library, program, etc. was replaced by another one by
manually overwriting the one delivered with a package. I've seen in with
openssl and other libraries. Like it or not that's the reality.
So for example a new package A I want to install depends on openssl
package.... but openssl is already there "installed" manually.
If you've installed unpackaged file somewhere that a package wants to
install files, then the package system will move those files to the
/var/pkg/lost+found directory and install the package's files. So that
shouldn't be an issue.
Then sometimes it is about broken dependencies as Peter pointed out.
I know you can file in a bug, contact maintainer, etc. but quite often
there is no time for it as you need an upgrade to happen *now* and not
when maintainer gets back to you, a changes gots approved, integrated
which might be anything between couple of days to couple of years or
never. --force of --nodeps fixex an issue now even if temporarily. Lack
of such functionality is only going to be a frustrating experience in
cases when mostly needed.
The issue of --force and --no-deps is that if you use it 'now' to 'fix'
something that's broken, your system will be forever broken later until
you actually do it right.
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
