[MacPorts] #62798: freeciv 2.6.4: man freeciv-gtk2 etc. "can't open" "No such file or directory" (.so directive and .gz?)

[MacPorts]

#62798: freeciv 2.6.4: man freeciv-gtk2 etc. "can't open" "No such file or
directory" (.so directive and .gz?)
----------------------+--------------------
  Reporter:  JDLH     |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.6.4
Resolution:           |   Keywords:
      Port:  freeciv  |
----------------------+--------------------

Comment (by JDLH):

 It appears that there is a convention of sorts to compress man pages. See
 the **man 5 groff-files**, section "Compression_of_roff_Files"
 https://www.man7.org/linux/man-
 pages/man5/groff_filenames.5.html#Compression_of_roff_Files .

 There is a utility **soelim** which can read groff source files, and do
 the include operation requested by `.so`. https://www.man7.org/linux/man-
 pages/man1/soelim.1.html . Maybe the freeciv port could run **soelim** on
 the affected man pages, before destrooting? Is **soelim** available as a
 standard part of MacPorts, or would the **groff** port need to become a
 build dependency?

 Or even one could make a patch which does the same thing, i.e. replaces
 that one line of each affected man source file by a copy of the **freeciv-
 client** man source file.

 > if there is some established workaround Portfiles use …

 It would be interesting to search through the source code of many ports to
 find other ports which use `.so` requests in their manpages. But all that
 is in the MacPorts ports repository is portfiles, and patches, not the
 entire source code of each port. Is there some place where all the source
 code is assembled, that I could do a search on?

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