On 4/18/12 2:08 PM, Danek Duvall wrote:
Philip Brown wrote:
If you compare the output of
pkg search basename:pkgrepo
vs
pkg search path:/usr/bin/pkgrepo
Both give the *exact same output*. Now as a long time systems
programmer, I can understand the difference between "basename" and
"path". But even I expect, that if something is indexed completely
differently, on supposedly different values.. it should have different
output for the 'value' column.
I don't understand why. The "value" is the key attribute of the object it
refers to, which is the path attribute in this case. I don't see why the
fact that the object can be found in different ways should result in a
different name for the object.
I think you are talking about consistency from an internals point of view.
ie: "Objects", in respect to "objects in a database."
I'm more concerned with the userlevel view. ie: consistency between user
input, and program output.
Also, what you said is, in a strict sense, not true. For
pkg search basename:xxx
The VALUE field output, is NOT the key. It's the associated keyed data.
That's why it is confusing to the user. Because there is no reference to
the *real* key involved.
Given that, I think it would be more comprehensible if the output was
altered as follows:
pkg search path:/some/path/name
(output unchanged from now, except to add initial slash)
INDEX ACTION VALUE PACKAGE
path file /some/path/name pkg:/blah/blah
pkg search basename:name
(output changed, to have initial slash, AND action field changed to real
key)
INDEX ACTION VALUE PACKAGE
basename name /some/path/name pkg:/blah/blah
Additionally, you might consider changing the labeling of the columns
entirely, so that there is a more consistent naming set, such as
INDEX_NAME KEY VALUE PACKAGE
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
