Date: Tue, 17 May 2022 12:54:06 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "Pat Maddox" <pat@patmaddox.com> Cc: erlang <freebsd-erlang@FreeBSD.org> Subject: Re: package mix release works, port doesn't? (and neither is self-contained) Message-ID: <c652213f-c10e-4a52-b2a2-fcf112cf7b4b@www.fastmail.com> In-Reply-To: <7814C787-2101-45DC-971D-2571E29EF4F6@patmaddox.com> References: <42EA9771-2440-49D3-BEFA-05A888F8D90A@patmaddox.com> <A20A5B06-676E-4AF8-940A-3992194B1E80@patmaddox.com> <d2915f8a-2280-4c23-a251-645f1efd0185@www.fastmail.com> <9B6718AD-FC61-4DBC-8DF1-9FF0E207B945@patmaddox.com> <7814C787-2101-45DC-971D-2571E29EF4F6@patmaddox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 5 May 2022, at 10:41, Pat Maddox wrote: > On 4 May 2022, at 23:48, Pat Maddox wrote: > However, the port replaces it: > https://cgit.freebsd.org/ports/tree/lang/elixir-devel/Makefile#n48 > > So where mix release produces the following lines in > ex_ample/releases/0.1.0/elixir: > > ERTS_BIN= > ERTS_BIN="$SCRIPT_PATH"/../../erts-12.3./bin/ > > The port changes them to: > > ERTS_BIN=/usr/local/lib/erlang24/bin/ I think I'm missing something here about how this is setup / deployed & used. when you build a release, it shouldn't end up with an elixir-specific PATH embedded in it, and if that does happen we should fix that. lang/elixir-devel is hardwired because the BEAM bytecode varies across releases, and we need to both build & run with the new shiny OTP versions, rather than whatever versions you have installed. but the OTP release machinery should assemble you a release with the correct bits either way. At least log an issue for this on bugs.freebsd.org (per my other email to list) and we will fix it. A+ Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c652213f-c10e-4a52-b2a2-fcf112cf7b4b>