[MacPorts] #62984: freeciv @2.6.4_0: propose a major restructure to provide all 12 clients and utilities

[MacPorts]

#62984: freeciv @2.6.4_0: propose a major restructure to provide all 12 clients and
utilities
--------------------------+----------------------
  Reporter:  JDLH         |      Owner:  JDLH
      Type:  enhancement  |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.7.1
Resolution:               |   Keywords:
      Port:  freeciv      |
--------------------------+----------------------

Comment (by tdprime):

 I have taken a look at a few distributions to see how they have organized
 packages for freeciv.

 FreeBSD uses a scheme that matches what was first described above. Their
 package system calls them "options". MacPorts calls them "variants". They
 do have a constraint that at least one client flavour be selected. FreeBSD
 does have a server only, "no_x11", package which has no client/UI
 variants.

 In addition to client variants, FreeBSD also gives options to set the
 backend database. This is used when user authentication is enabled for the
 server.

 Ubuntu's debian packages are organized as separate packages for each
 installable. This is necessary because the package system doesn't support
 variants (or options). Each client package is named with "-client-". For
 example, freeciv-client-gtk4. In addition to their unique depencencies,
 each client depends on a common set: freeciv-data, freeciv-server,
 freeciv-client-extras.

 Lastly, I did look at homebrew. One package, no options. The only lesson
 there is, don't do it that way.

 One can see similarities in jmroot's suggestions (see comment:2) with
 Ubuntu's organization.

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