On Tue, 2006-12-05 at 21:56 +0000, Grant Edwards wrote: > On 2006-12-05, Alan McKinnon <[EMAIL PROTECTED]> wrote: > > >> That's nasty. Why do some equery commands accept regexes and > >> others dont? > > > > Because some equery commands search for packages (ideally > > suited for a regex), and others by design operate on a single > > package (where using regexes don't make any sense). > > But that differentiation seems purely artificial. What is > there about the "print size" operation that makes it something > you can't or shouldn't do on multiple packages? Why shouldn't > the operation of "pkgspec" and "command" be orthogonal? > "pkgspec" selects zero or more packages and the command > operates on the selected package. > > Why the limitation that some commands only operate on one > package? > > > It all makes perfect sense when you realize this, but no-one > > expects you to realize it immediately :-) > > Well, it seems pretty non-intuitive and non-orthogonal to me. I > guess that's a result of many years of shell usage where > commands like "rm" and "ls" work equally well on a single file > or multiple files.
Okay, I've modified the size command to accept regular expressions and basically work like the equery list command. I will look at what needs to be done for the other commands as well. $ svn commit -m "Modify equery size command to work like the equery list command for pkgspec arguments" Sending ChangeLog Sending src/equery/equery Sending src/equery/equery.1 Transmitting file data ... Committed revision 325. Regards, Paul
signature.asc
Description: This is a digitally signed message part
