Comment # 15
on bug 12746
from Guy Harris
(In reply to Uli Heilmeier from comment #3)
> The 'Wireshark 2.0.6 Intel 64.dmg' includes the manpages in the directory
> 'Wireshark.app/Contents/Resources/share/man/'.
>
> The 'Wireshark 2.2.0 Intel 64.dmg' doesn't include any manpage. The
> directory 'Wireshark.app/Contents/Resources/share/man/' is missing.
>
> Furthermore in the installer scripts code to extend the MANPATH is missing.
> I guess '/etc/manpaths.d/' should be used for this.
Except that it doesn't actually *work* - /etc/paths.d and /etc/manpaths.d are
scanned by the path_helper program in /etc/profile, /etc/csh.login, and
/etc/zprofile, and path_helper doesn't generate commands to set MANPATH unless
MANPATH is already set in path_helper's environment, which it isn't at the time
those scripts are run by a login shell.
However, the man command on macOS (which is actually a *Linux* version, not a
*BSD* version) will set the search path based on the setting of PATH, so *if*
PATH were to include Wireshark.app/Contents/Resources/bin, it would search in
Wireshark.app/Contents/Resources/share/man.
As of change I7202b5a0fe5d2b90c956dc0db2af073f6c08b00d, the app bundle includes
a Wireshark.app/Contents/Resources/bin directory, with symlinks to binaries in
Wireshark.app/Contents/MacOS, and sets /etc/paths.d/Wireshark to point to the
Wireshark.app/Contents/Resources/bin directory, so the man command should find
the Wireshark man pages in 2.2.4 and later.
You are receiving this mail because:
- You are watching all bug changes.