On 02/28/11 05:21 PM, Alan Coopersmith wrote:
On 02/28/11 08:11 AM, Gary Pennington wrote:
Hi,
I would expect pkg search to tell me which package delivered the perl binary,
but:
file exists:
bash-4.1$ ls -l /usr/perl5/bin/perl
-r-xr-xr-x 2 root bin 18756 Feb 28 2011 /usr/perl5/bin/perl
That's not the real path to it though:
lrwxrwxrwx 1 root root 11 Feb 18 2010 /usr/perl5/bin ->
./5.8.4/bin/
% readlink -f /usr/perl5/bin/perl
/usr/perl5/5.8.4/bin/perl
% pkg search -l '</usr/perl5/5.8.4/bin/perl>'
PACKAGE PUBLISHER
pkg:/runtime/[email protected]
Thanks for the answers.
I'm searching by path, because I'm writing some code to examine why
packages depend on other packages and I need to specify the path.
Interestingly, pkgdepend finds a dependency on perl at the path I
documented so I just assumed that pkgdepend had found a binary.
Here's the line from the pkgdepend .dep file output from nightly:
depend fmri=__TBD pkg.debug.depend.file=perl
pkg.debug.depend.path=usr/perl5/bin
pkg.debug.depend.reason=usr/bin/pgstat pkg.debug.depend.type=script
type=require
That makes me now wonder if pkgdepend is doing the right thing. Also, I
wonder now how pkgdepend goes on to resolve this dependency correctly?
I'm trying to figure out which package "__TBD" represents using pkg
search for the path and the file. Perhaps there is a better way to do this?
(If you are curious why I'm doing this. It's so I can examine specific
(i.e. action level) dependencies rather than seeing the output of
resolve which reduces all specific action dependencies to package
dependencies. i.e. I'd like to see all the detail under the discovered
package dependencies.)
Gary
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
