[MacPorts] #54566: ipfs @0.4.10 : global, versioned, peer-to-peer filesystem

[MacPorts]

#54566: ipfs @0.4.10 : global, versioned, peer-to-peer filesystem
-------------------------+-----------------
  Reporter:  1-61803     |      Owner:
      Type:  submission  |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  ipfs        |
-------------------------+-----------------

Comment (by raimue):

 As [https://lists.macports.org/pipermail/macports-
 dev/2017-August/036217.html discussed on macports-dev], you cannot use
 `$user_home`. The startupitem probably needs to be fixed to store its data
 in `${prefix}/var/ipfs` or similar. If I read the Portfile correctly, this
 will currently even run the daemon as root, which should be avoided.
 Create a separate user with `add_user` and specify to use that in the
 LaunchDaemon.

 Actually, [https://github.com/ipfs/go-
 ipfs/blob/master/misc/launchd/install.sh upstream] does not install this
 as a LaunchDaemon (system-wide), but as a LaunchAgent (per-user). This
 might make more sense, but I do not know what this software is supposed to
 do.

 In any case, the number of reinplace statements make it look like it would
 be easier to maintain a custom `.plist` file (or create one using
 `startupitem.*`) instead of editing all of the key/value pairs with
 regular expressions.

 The installation of the startupitem should also respect
 `startupitem_install` as set in macports.conf.

 The bash-completion file should be installed as `${prefix}/share/bash-
 completion/completions/ipfs` in order to load it automatically on demand.
 The note can then be removed as no user interaction will be required.

 Is the `go` port really required at runtime? I thought Go would just
 compile and link a binary. If so, it should be moved to `depends_build`.

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