Danek Duvall wrote:
I have a feeling that most people who use "pkg contents" just pipe it
through grep or less to look for individual actions if they're looking for
something in particular, but I've been frustrated by the need for that, and
the fact that coming up with the right regular expression is a bit of a
pain ("\<path=[^ ]*/ls", for instance).
So I've been dreaming about an option to contents that allows you to filter
by attribute value. So I could say, for instance:
pkg contents -o path,target -a path=\*.desktop openoffice
...
PATH TARGET
...
usr/share/applications/openoffice.org3-writer.desktop
../../../opt/openoffice.org3/share/xdg/writer.desktop
Does this strike anyone but me as useful? Confusing?
I certainly think it is useful. The only thing that makes this less
useful is that there is no indication of which package the match was
found in. While I agree search should be able to do this too, contents
offers a few options that search does not (such as being able to
restrict the package to multiple specific packages easily afaik). In
other words, 'pkg contents pkg1 pkg2 pkg3 ... -o ... -a ...'.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
