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 ...

Maxim Sobolev sobomax at
Wed Jun 4 19:55:02 UTC 2008

Remko Lodder wrote:
>> Where do we stop?  Should we add long options to all
>> /usr/bin utilities?  Why stop at /usr/bin, let's add
>> long options to /usr/sbin, /bin, /sbin, /rescue, etc.
> That is not your call. If a maintainer wants to add all options he can 
> consider, he is free to do so. Though others might not appreciate that 
> as much as he does. It can be discussed ofcourse, but to a certain extend.

It's not your call either. We have style(9), which says:

      For consistency, getopt(3) should be used to parse options.  Options
      should be sorted in the getopt(3) call and the switch statement, 
      parts of the switch cascade.  Elements in a switch statement that 
      should have a FALLTHROUGH comment.  Numerical arguments should be 
      for accuracy.  Code that cannot be reached should have a 

There is nothing about getopt_long(3) being acceptable 
replacement/addition to the getopt(3).


More information about the cvs-src mailing list