[MacPorts] #57698: CI: Use the normal MacPorts installer (was: Travis: Use the normal MacPorts installer)

[MacPorts]

#57698: CI: Use the normal MacPorts installer
-----------------------------+----------------------
  Reporter:  ryandesign      |      Owner:  admin@…
      Type:  defect          |     Status:  reopened
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------
Changes (by ryandesign):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 Replying to [comment:13 l2dy]:
 > Travis CI has been removed from our repositories.

 But we still use a custom MacPorts installer for GitHub Actions CI where
 the same situation still applies.


 Replying to [comment:10 ryandesign]:
 > Replying to [comment:7 l2dy]:
 > > > Ok, so if we had a way of preventing selfupdate when using the pkg
 installer, we could use that?
 > >
 > > Sure. That's the only reason preventing us from using the pkg
 installers.
 >
 > I'll see what I can do about adding this to the installer pkg. I have
 some ideas.

 An installer pkg can contain subpackages. The installer can offer the user
 a choice in the GUI of which subpackages to install or it can make its own
 choices. Those choices can be overridden when invoking `installer` on the
 command line. My idea was that we could move `selfupdate` to a separate
 pkg that the installer would usually run automatically, except we could
 choose not to run it in CI. Separate installer subpackages would also be
 useful for allowing the user to choose which mirror they want to use
 (#49496) or whether they would like to autoinstall the mpstats port. These
 enhancements are difficult to implement without overhauling the way the
 pkg is created (#56055).

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