Date: Sat, 31 May 2008 11:50:29 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Joerg Sonnenberger <joerg@britannica.bec.de> Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/usr.sbin/pkg_install/add main.c pkg_add.1 src/usr.sbin/pkg_install/create main.c pkg_create.1 src/usr.sbin/pkg_install/delete main.c pkg_delete.1 src/usr.sbin/pkg_install/info main.c pkg_info.1 ... Message-ID: <20080531185029.GA95548@troutmask.apl.washington.edu> In-Reply-To: <20080531180429.GA2240@britannica.bec.de> References: <200805301426.m4UEQ92d025434@repoman.freebsd.org> <48405C4B.3050603@FreeBSD.org> <20080531180429.GA2240@britannica.bec.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 31, 2008 at 08:04:29PM +0200, Joerg Sonnenberger wrote: > On Fri, May 30, 2008 at 12:58:03PM -0700, Maxim Sobolev wrote: > > I am curious what is our policy on using long options in the base system > > (if any)? I believe that pkg_install is the first non-contributed base > > system utility to actually widely use it. > > Consider what happens when you want to split -f into different options > that are more selective. Long options are more intuitive than random > letters for that purpose. > Won't one simply use optarg? In fact, getopt(3) shows an optarg example using -f. I admit that I had the same thoughts as Maxim. Why is a FreeBSD utility using long options? -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080531185029.GA95548>