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