On Fri, 2008-05-30 at 12:58 -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. For some reason I've got > impression that use of getopt_long is considered "the Linux/GNU way", > this API provided for compatibility purposes and its use in base system > is discouraged. Quick grep through /use/src seemingly supports that. > > Can someone confirm/reject? > > Florent Thoumie wrote: > > flz 2008-05-30 14:26:09 UTC > > > > FreeBSD src repository > > > > Modified files: > > usr.sbin/pkg_install/add main.c pkg_add.1 > > usr.sbin/pkg_install/create main.c pkg_create.1 > > usr.sbin/pkg_install/delete main.c pkg_delete.1 > > usr.sbin/pkg_install/info main.c pkg_info.1 > > usr.sbin/pkg_install/lib lib.h > > usr.sbin/pkg_install/updating main.c pkg_updating.1 > > usr.sbin/pkg_install/version main.c pkg_version.1 > > Log: > > - Add long options to pkg_install. > > - Remove check for '-?' as it's not listed in authorized options. > > - Bump PKG_INSTALL_VERSION to 20080530. > > -Maxim >
I am not sure about policy, however I do appreciate the long options sometimes. Primarily, I think they are useful (in a self-documenting way) for use in shell scripts. I tend to prefer the single-char options when I am doing the administration myself. -- Coleman Kane
signature.asc
Description: This is a digitally signed message part
