[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
Resolution:               |   Keywords:
      Port:  freeciv      |
--------------------------+--------------------

Comment (by JDLH):

 I see the logic of that. I guess MacPorts is fundamentally about porting
 the upstream content, not reauthoring it.

 But in the case of freeciv, the MacPorts ports pick and choose what to
 bring along from upstream. Just two clients of the six or so on offer.
 Some but not all of the ancillary tools. It would be nice if MacPorts
 would at least allude to that in the "port info" output.

 Freeciv can't be the only port in this situation. Are there other ports
 which install many components, or a very different subset than the
 upstream project installs? How do those ports communicate to the user
 about what MacPorts does?

 Freeciv could document better. They could create a manpage "freeciv", so
 that "man freeciv" would introduce the user to the variety of clients and
 ancillary tools. I can take this up with the freeciv project upstream.

 Would it be reasonable to at least add a sentence to the long_description
 saying something like, "Run 'man freeciv-client' for more information."?

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