Hi
Thanks good idea to use the -v to keep track of this.
Enda
On 21/06/2011 17:38, Shawn Walker wrote:
On 06/21/11 09:28, Enda o'Connor - Sun Microsystems Ireland - Software
Engineer wrote:
Hi
So on build 167 I added library/perl-5/database-512
this installed two packages ( didn't tell me the second package it blew
on ), then I ran pkg uninstall database-512 which removed just
database-512, leaving the required package ( I'm guessign
runtime/perl-512 ) installed, so is there a way to
1 see what dependencies a package has ( I guess some variant of pkg
content )
You can see the immediate dependencies of a package like this:
pkg contents -H -t depend -o fmri $PKG_NAME
But that doesn't help much since those dependencies may have depedencies...
2 blow away dependencies as well, or at least see what they are.
This is probably a dangerous option though, but nice tobe able to see
what got installed with the pkg I want to blow away. MAybe just be able
to list the dependencies.
There is no option to remove dependencies automatically.
3 pkg install to say what it actually installed out of any given
dependencies that a package might have.
Use -nv to perform a dry-run of operations such as install and see what
will be installed, or simply -v while installing:
pkg install -nv ...
pkg update -nv ...
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
