On Fri, Mar 06, 2009 at 05:55:52PM -0800, Brock Pytlik wrote: > 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.
Why do you have the "<>" syntax at all? I would completely expect to define the result type with a flag to the search subcommand. What happens if you search for "<token1> AND token2"? I think you should put a couple of examples of the new search stuff in pkg(1). In fact, you might have to clean up the search example that's there; I'm not sure if it's correct now. > Also, right now I'm packaing ply up as part of SUNWipkg since it's needed > for the client, but not the server. If that's not the right packaging > approach to take, please let me know. I wasn't sure if I should but it into > a second package or not. It should probably be in its own package. SUNWply is fine for now. Do you have a deadline for code review comments? Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
