On Sun, 7 Dec 2008 12:44:25 +0900 "Douglas Anderson" <[EMAIL PROTECTED]> wrote:
> I also thought about renaming the "list(l)" option as "search", > because if you look at the help output, almost every module "lists" > something. equery's "list" is actually a search, I don't see why we > shouldn't name it that. I think maybe list was used because there were > already two "s" options, stats and size. Stats is not implemented so > I'm taking it out of help for now. Size can use the short "z", becaues > that's quite unique. That would free up "s" for search and it would be > a whole lot clearer. > > Yes? No? No. "search" (if used at all) should be reserved for a more comprehensive search framework (though IMO a separate tool for that is more appropriate), not just a simple name match. "list" makes sense if you consider that the pkgspec argument is optional, and one of the main tasks of it is to simply list the packages in the given repository (that's why vardb is also the default for it) without further filtering. Also one of the main goals of equery (according to karltk, the original author) was to have a stable user interface, compared to the deprecated qpkg and etcat scripts. And while the equery interface isn't exactly the best I've seen it has been stable, so you might want to think twice before renaming options and eventually pissing off users or breaking third-party scripts. Marius
