[MacPorts] #63263: py-ansible-base 2.10.11: Path replacement breaks custom facts

[MacPorts]

#63263: py-ansible-base 2.10.11: Path replacement breaks custom facts
------------------------------+-------------------------
  Reporter:  F30              |      Owner:  adfernandes
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:                   |   Keywords:
      Port:  py-ansible-base  |
------------------------------+-------------------------

Comment (by F30):

 Replying to [comment:2 ryandesign]:
 > It is customary for ports in MacPorts to be programmed to look for
 configuration files and so forth within the MacPorts prefix (e.g. in
 /opt/local/etc rather than /etc). I don't know anything about ansible so
 if that is not appropriate for ansible it can certainly be changed. I
 defer to the maintainers.

 Adjusting the paths is certainly appropriate for **local** configuration
 on the machine where Ansible and MacPorts are installed. However, I'll
 argue that Ansible is special because it is used to execute code on
 **remote** hosts. Ansible facts, which we're talking about here, do get
 collected on the remote.

 Replying to [comment:3 adfernandes]:
 > I am not in favor of using the system `/etc` directory for anything.
 >
 > macOS is **not** Linux, not even POSIX, and as far as I know the
 similarities, use, and even ''existence'' of `/etc` is a bit of a
 coincidental anachronism.

 Well, the remote host might very well be Linux. In fact, it often is in
 practice. But it really could be anything – a default of
 "/opt/local/etc/ansible" on the remote will only work if it happens to be
 a Mac with MacPorts.

 > How many other Macports packages use the system `/etc` directory for ...
 anything?
 >
 > (I just checked my large collection of installed ports, and the answer
 is, I think, "none of them".)

 See above, this is not about local configuration on hosts with MacPorts
 installed.

 To me, saying the remote configuration path should be set by MacPorts
 feels a bit like saying `ssh` installed via MacPorts should add
 "/opt/homebrew/bin" to `$PATH` on remote hosts.

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