Shawn Walker wrote:
Brock Pytlik wrote:
Someone mentioned this morning that they hadn't realized I'd put out
a webrev that was more than an FYI one. My apologies for being unclear.
Anyway, this is a real webrev (ie, it passes the test suite, has been
pylinted, and I've made an effort to cleanup and remove dead code).
Specific things I still have questions remaining about:
Should I include/allow the -a/-p command options which duplicate the
functionality of putting '<>' or not around the entire query? Right
now, I'm leaning towards removing these options and simply relying on
<>. The reason for having -a/-p would be if we wanted to make
returning lists of packages the default behavior, and have users have
to specify -a to get the traditional behavior.
I have to agree with Danek; '<>' might be nice for a power-user, but
it's going to be rather opaque for most. I would expect a command
line flag to determine how the results are returned.
Some more examples of different combinations of using '<>' and not
using '<>' are needed.
I'm planning on adding more of these.
Cheers,
Ok, I'll keep the command line flag -p then and add it to the man page
and usage.
'<>' is not redundant then because '<foo> AND <bar>' is different than
'<foo AND bar>'
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
