Re: extcap command line parameter format

[Guy Harris <guy () alum mit edu>]

On Jul 23, 2018, at 11:37 AM, Guy Harris <guy () alum mit edu> wrote:

> On Jul 20, 2018, at 10:12 AM, Jaap Keuter <jaap.keuter () xs4all nl> wrote:
>
> > If so this could require changes across the board, changes to documentation (docbook, man page) in the least.
>
> Yes.

docbook/wsdg_src/WSDG_chapter_capture.asciidoc fixed in change https://code.wireshark.org/review/28864.

No man page I could find mentions the optional argument to --extcap-version.

No help message I could find does so, either.

Third-party extcap programs will have to change if 1) they don't happen to support --extcap-version=XXX already and 2) 
they are to work with the not-yet-released Wireshark 3.0.  Note that if they're using getopt_long(), they will 
*automatically* support it; the GNU libc version of getopt_long(), the *BSD/macOS version of getopt_long(), and the 
Solaris version of getopt_long() all support --longopt=value, and on Windows and other UN*Xes, which don't have 
getopt_long(), the extcap program will use the GNU libc version that we supply.  Note, BTW, that if they don't support 
*either* --extcap-version=XXX *or* --extcap-version XXX, they'll also have to change, no matter whether we use =XXX or 
" XXX"....

So what *else* needs to change?

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe