[MacPorts] #44060: Erlang binaries missing from the PATH environment
#44060: Erlang binaries missing from the PATH environment ------------------------+-------------------------------- Reporter: conradwt@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: 17.0_1 | Port: erlang ------------------------+-------------------------------- Hi, epmd isn't being added to the PATH environment and not automatically started for the Erlang process. This issue appears to have started with R17.0_1 because I haven't seen this issue in prior releases. -- Ticket URL: <https://trac.macports.org/ticket/44060> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang binaries missing from the PATH environment -------------------------+-------------------------------- Reporter: conradwt@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: 17.0_1 Port: erlang | -------------------------+-------------------------------- Comment (by conradwt@…): Shouldn't all the relevant binaries from /opt/local/lib/erlang/erts-6.0/bin be added to the PATH environment? -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang @ 17.0_1: epmd binary missing from the PATH environment -------------------------+------------------------- Reporter: conradwt@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: erlang | -------------------------+------------------------- Changes (by ciserlohn@…): * keywords: 17.0_1 => * owner: macports-tickets@… => ciserlohn@… * cc: ciserlohn@… (removed) -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang @ 17.0_1: epmd binary missing from the PATH environment -------------------------+------------------------- Reporter: conradwt@… | Owner: ciserlohn@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: invalid | Keywords: Port: erlang | -------------------------+------------------------- Changes (by ciserlohn@…): * status: new => closed * resolution: => invalid Comment: Looking at the svn history it seems that epmd hasn't been in PATH since r30481 (Erlang R11B; 2007). Epmd starts up automatically just fine: {{{ $ erl -name abc@localhost -noshell & [1] 74550 $ ps ax | grep erl 74556 ?? S 0:00.00 /opt/local/lib/erlang/erts-6.0/bin/epmd -daemon 74550 s004 T 0:00.13 /opt/local/lib/erlang/erts-6.0/bin/beam.smp -- -root /opt/local/lib/erlang -progname erl -- -home /Users/ci -- -name abc@localhost -noshell }}} Did you forgot the {{{-name}}} option? -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang @ 17.0_1: epmd binary missing from the PATH environment -------------------------+------------------------- Reporter: conradwt@… | Owner: ciserlohn@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: invalid | Keywords: Port: erlang | -------------------------+------------------------- Comment (by jose.valim@…): There are many situations having epmd in the $PATH is handy. 1. epmd is only automatically started if you pass the -name on startup. If you are programatically starting the node, for example by using net_kernel:start/1, you need to have started epmd explicitly before; 2. You can pass commands to epmd, for example, to change the running port or get all available names. More info here: http://www.erlang.org/doc/man/epmd.html; All Erlang packages I have seen so far do have epmd installed to bin. There are also tools like rebar (https://github.com/rebar/rebar/blob/master/priv/templates/simplenode.nodetoo...) that expects epmd to be in the path (exactly due to 1 above). Please revisit the decision of not including epmd. :) -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang @ 17.0_1: epmd binary missing from the PATH environment -------------------------+------------------------- Reporter: conradwt@… | Owner: ciserlohn@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: invalid | Keywords: Port: erlang | -------------------------+------------------------- Comment (by paulschoenfelder@…): I agree with José on this 100%. I don't think it makes sense to differ from the way Erlang is packaged elsewhere. Installing an Erlang package should always do more or less the same thing regardless of what you use to install it. It seems that right now MacPorts is the only package manager which does something different (as far as I can tell), and I'm not sure what the motivation is for doing so. -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#44060: Erlang @ 17.0_1: epmd binary missing from the PATH environment -------------------------+------------------------- Reporter: conradwt@… | Owner: ciserlohn@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: invalid | Keywords: Port: erlang | -------------------------+------------------------- Comment (by ciserlohn@…): Erlang 17.1 (r121448) makes the epmd binary available in PATH. -- Ticket URL: <https://trac.macports.org/ticket/44060#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts