Awesome, thanks. I'm fine with either -T or --timeout. I think I used a -- option when I had to add something that I didn't expect to be used often, but no idea whether that was the right thing to do or not.
-j On Mon, Apr 07, 2008 at 01:30:08PM -0700, Danek Duvall wrote: > On Mon, Apr 07, 2008 at 01:23:58PM -0700, [EMAIL PROTECTED] wrote: > > > a) Comment the units of measurement for the timeout. Is this 30 > > seconds, or some other number? > > Seconds. Done. > > > b) If 30 is the default, allow the user to override the default by > > adding a command-line option. I'm assuming we'd only need to use this > > in a situation where we guessed wrong about the timeout. In such a > > case, it would be better to have a command-line option than to require > > the user to change the code. > > How's -T work? Or should I make it --timeout so we don't waste a > single-letter option? I doubt this would be used much, but I'm not sure > where Stephen was going with this in terms of a usage model. > > Danek > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
