[MacPorts] #62793: freeciv 2.6.4: port info doesn't explain the list of executable programs

[MacPorts]

#62793: freeciv 2.6.4: port info doesn't explain the list of executable programs
-------------------------+---------------------
 Reporter:  JDLH         |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  Low          |  Milestone:
Component:  ports        |    Version:  2.6.4
 Keywords:               |       Port:  freeciv
-------------------------+---------------------
 The **freeciv** and **freeciv-x11** ports install a number of executable
 programs and three man pages. But none of the information MacPorts
 supplies names those programs. Thus it's hard to figure out how to use
 freeciv once it is installed.

 Executable programs installed by **freeciv** port: freeciv-sdl2 (or
 freeciv-sdl on older OSs), freeciv-mp-cli .

 Executable programs installed by **freeciv-x11** port: freeciv-gtk2,
 freeciv-mp-gtk2 .

 Executable programs installed by both ports: freeciv-manual, freeciv-
 server .

 Man pages installed by both ports: freeciv-client, freeciv-server,
 freeciv-modpack, freeciv-manual, freeciv-ruledit, and presently garbled
 forms of: freeciv-gtk2, freeciv-gtk3.22, freeciv-gtk3, freeciv-mp-cli,
 freeciv-mp-gtk2, freeciv-mp-gtk3, freeciv-mp-qt, freeciv-qt, freeciv-
 ruledit, freeciv-sdl, freeciv-sdl2, freeciv-xaw .

 The most fundamental thing to tell users is: for the **freeciv** port, run
 `freeciv-sdl2` or `freeciv-sdl`; for the **freeciv-x11** port, run
 `freeciv-gtk2`.

 I can think of two ways to include this information:

 1. Add several more lines with this information to the `long_description`
 string in the Portfile.

 2. Create a new man file `freeciv` which explains how MacPorts has
 installed all the various parts, and how to find them.

 Which is the better approach?  I'm willing to submit a patched Portfile.

-- 
Ticket URL: <https://trac.macports.org/ticket/62793>
MacPorts <https://www.macports.org/>
Ports system for macOS