On Thu, Oct 23, 2008 at 04:42:15AM +0100, John Levon wrote: > pkg contents is kind of hard to use. It feels more like a scripting > interface. A perfect example of this is: > > # pkg contents -t depend SUNWxvm > PATH
Yeah, that's pretty sucky. > Maybe I'm just asking for a few RFEs (smarter column selection, inverse > dependency listing, help that enumerates possible -t and -o values), > though. Those are all good RFEs (search actually covers the reverse dependencies, but not at all intuitively), but some ideas on how they might work are greatly appreciated. Given that -o values can be absolutely anything, what should we suggest? -t is much more constrained, but at least those are completely documented in the man page, and so verbose help seems less useful. As for smarter column listing, what would you suggest? Perhaps we could have a default column listing for each action type -- "-t depend" could imply "-o fmri", maybe -- but then what about -t link,depend? Should the default output (no -t option) have all types or just actions with paths? I'm thinking that perhaps we should have a -l (long) option akin to ls that gives you a multicolumn output by default, giving similar output to ls for filesystem objects, and both fmri and type for dependencies, etc. And perhaps a -a option that tells it to list all types? Maybe prefixing each line with the action type? What about if -t isn't specified, but -o is, then only actions with attributes named in -o are printed -- so you can do pkg contents -o path. Other ideas? Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
