portclippy knows only one command line option: --strict However, the behavior when giving unknown options seems broken: While unknown options with just one '-' produce output like this: root@dev:~# portclippy -blub portclippy: invalid option -- b usage: portclippy [--strict] [Makefile] If you give anything other than --strict using '--', it will just crash: root@dev:~# portclippy --blub Bus error (core dumped) (Arguably, even in the first instance, it seems weird the message complains about the command line as if only one letter had been given.) I have only tested this on 13.0-RELEASE on amd64.
Sigh, I forgot to terminate longopts. Thanks for the report. Fixed in https://github.com/t6/portfmt/commit/8fe7439a7e783dacff988c50820877182327b98e > (Arguably, even in the first instance, it seems weird the message complains about the command line as if only one letter had been given.) That's just normal getopt_long() behavior. Compare with any other command that uses it. For example: $ ls -zap ls: invalid option -- z