On 2023/03/07 10:33:20 +0100, Volker Schlecht <openbsd-po...@schlecht.dev>
wrote:
> Would the attached change to erlang.port.mk address the issue in a more
> general way?
>
> Index: erlang.port.mk
> ===================================================================
> RCS file: /cvs/ports/lang/erlang/erlang.port.mk,v
> retrieving revision 1.31
> diff -u -p -r1.31 erlang.port.mk
> --- erlang.port.mk 16 Jan 2023 18:27:29 -0000 1.31
> +++ erlang.port.mk 7 Mar 2023 09:30:35 -0000
> @@ -43,6 +43,7 @@ REBAR_BIN ?= ${LOCALBASE}/bin/rebar3-${
> # Make sure rebar gets called as 'rebar3', otherwise escript tries to call
> the
> # binary name (e.g. rebar3-25) as the script entrypoint.
> _MODERL_LINKS += rebar3-${MODERL_VERSION} rebar
> +_MODERL_LINKS += rebar3-${MODERL_VERSION} rebar3
> .endif
>
> # Append the flavor to all the Erlang dependencies
Yeah, it should help. I suspect most upstream will just use `rebar3'.
Will test this later when i'll get the time to look at the erlang
update, but it's ok op@ if someone wants to go ahead with it in the
meantime (provided it doesn't break other ports.)
