I was reading pkg_sign.1 and noticed that the description for the -o option seems incorrect. The current pkg_sign.1 text says under the -o option that "Otherwise, unsigned packages are created in the current directory" where I think it should say "Otherwise, signed packages are created in the current directory." It is possible I am misunderstanding the text and, in that case, further clarification is needed. If the -o option is omitted, are packages signed and then that new signed package replaces the previously unsigned package in the current directory? Attached is a patch that corrects the text according to my understanding of it.
Bryan Index: usr.sbin/pkg_add/pkg_sign.1 =================================================================== RCS file: /cvs/src/usr.sbin/pkg_add/pkg_sign.1,v retrieving revision 1.10 diff -u -p -r1.10 pkg_sign.1 --- usr.sbin/pkg_add/pkg_sign.1 15 Feb 2017 13:19:08 -0000 1.10 +++ usr.sbin/pkg_add/pkg_sign.1 9 Oct 2017 22:49:13 -0000 @@ -68,7 +68,7 @@ in the listing. Sign existing packages in parallel. .It Fl o Ar dir Specify output directory for signing packages. -Otherwise, unsigned packages are created in the current directory. +Otherwise, signed packages are created in the current directory. .It Fl S Ar source Source repository for packages to be signed. .\" This can be any url admissible for a
