[MacPorts] #66334: /opt/local/bin/ssh-agent not used on macOS 10.13.6
MacPorts
noreply at macports.org
Tue Jul 2 03:39:09 UTC 2024
#66334: /opt/local/bin/ssh-agent not used on macOS 10.13.6
-------------------------+-----------------------
Reporter: ianstyxial | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.8.0
Resolution: | Keywords: ssh-agent
Port: openssh |
-------------------------+-----------------------
Comment (by fhgwright):
It makes sense that the agent isn't automatically included in `port load`,
but it would be useful if there were another `port load` target for it. I
have a working setup for it here, though I haven't determined whether
there's a way to duplicate the behavior of PATH, where the MacPorts
version of a command is used if it's active, and the OS-supplied version
otherwise.
I just made a modified version of the Apple LaunchAgent, as follows:
{{{
MacPro:~ fw$ diff /System/Library/LaunchAgents/org.openbsd.ssh-agent.plist
/Library/LaunchAgents/org.macports.ssh-agent.plist
6c6
< <string>org.openbsd.ssh-agent</string>
---
> <string>org.macports.ssh-agent</string>
9c9
< <string>/usr/bin/ssh-agent</string>
---
> <string>/opt/local/bin/ssh-agent</string>
}}}
With that, one just unloads the system version and loads the MacPorts
version, though there's no automatic fallback if the MacPorts version is
deactivated.
The separate target issue could probably be solved just by creating a
dummy subport for the agent load.
--
Ticket URL: <https://trac.macports.org/ticket/66334#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list