Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 132192 - equery options unclear / non-obvious, could be expanded
Summary: equery options unclear / non-obvious, could be expanded
Status: RESOLVED DUPLICATE of bug 269071
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: Lowest enhancement (vote)
Assignee: Portage Tools Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-03 19:16 UTC by Danny Sauer
Modified: 2009-05-25 22:02 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Danny Sauer 2006-05-03 19:16:27 UTC
For months I've tried to determine how to replace "etcat -v" with an equivalent equery command, but have failed.  Doing "equery --help" shows some options, and it's presumed that the help is fairly complete based on the length of the output.  But tonight I looked at the man page (after seeing my question answered using some flags that I didn't know existed), and found that it's not.

Lines like
  "list(l) <local-opts> pkgspec - list all packages matching pkgspec"
should probably be rewritten more in the style of other *nix commands, where instead of <local-opts> there is a bracketed list of actual options.  Such as [-i -I -p -o -f -e -d] or [-<iIpofed>]  It doesn't take much more space to include something like that, and it would be much more helpful.  It would be helpfu to the new user, in that it would give her something to look up on the man page; and would be helpful to an experienced user in jogging his memory as to which letter those developers used.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-05-04 00:00:30 UTC
Not a documentation product bug.
Comment 2 michael@smith-li.com 2009-05-25 22:02:20 UTC
Let's call this solved when 269071 is resolved. They're not exactly the same thing, but this one will never be resolved on its own. Rather, the rewrite of equery and its subsequent documentation rewrite should illuminate problems like this...

*** This bug has been marked as a duplicate of bug 269071 ***