[MacPorts] #58758: wireshark3 3.0.2_1: no "wireshark" executable (just Wireshark.app)

[MacPorts]

#58758: wireshark3 3.0.2_1: no "wireshark" executable (just Wireshark.app)
--------------------------+--------------------
  Reporter:  ewenmcneill  |      Owner:  (none)
      Type:  enhancement  |     Status:  closed
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:  worksforme   |   Keywords:
      Port:  wireshark3   |
--------------------------+--------------------

Comment (by ewenmcneill):

 `/opt/local/Applications/Wireshark.app/Contents/MacOS/Wireshark` doesn't
 exactly roll off the fingers like "wire<TAB>" :-)

 `/opt/local/Applications/Wireshark.app/Contents/MacOS` isn't on my `$PATH`
 (nor is `/Applications/MacPorts/Wireshark.app/Contents/MacOS`  on my
 `$PATH`, which AFAICT is the equivalent on my system).  It doesn't seem
 like a particularly good idea to put a bunch of single-executable
 directories on my `$PATH` just for occasional use (since they'll
 potentially be searched for any command run).

 If you don't want to provide any backwards compatibility in how to run
 `wireshark` from the command line (ie, to `wireshark`/`wireshark2`
 packages), and to leave each user to reinvent a similar work around to
 mine themselves, then sure, `WONTFIX` this ticket.

 I only opened the ticket because it seemed like something that could be
 ''easily'' provided.  Even having the package do something like:

 {{{
     ln -s
 ${destroot}${applications_dir}/Wireshark.app/Contents/MacOS/Wireshark
 ${destroot}${prefix}/bin/wireshark
 }}}

 would provide useful backwards compatibility (note: lowercase `wireshark`,
 so it tab completes the way it used to -- even though macOS filesystems
 are normally case insensitive, `bash`'s tab completion assumes case
 sensitivity...).

 Either way, I've got my work around implemented (as
 `/usr/local/bin/wireshark`).  So I'm just trying to save others the pain
 of spending half an hour figuring out what happened to the ability to
 start `wireshark` from the command line like I did (at least twice).
 Maybe they'll just have to rely on Googling for the workaround.... :-)

 Ewen

-- 
Ticket URL: <https://trac.macports.org/ticket/58758#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS