Date: Fri, 3 Aug 2018 16:17:57 +0200 From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= <jean-sebastien.pedron@dumbbell.fr> To: freebsd-erlang@freebsd.org Subject: Re: Dumb question on erlang ports Message-ID: <fa6d6798-3e54-0713-345c-1e8ae2f0c2da@dumbbell.fr> In-Reply-To: <CAGipyQ_7Sbwf72QhRmOifH-mSefJsuCWwN_wmMibvVSv-Cj2wA@mail.gmail.com> References: <CAGipyQ_7Sbwf72QhRmOifH-mSefJsuCWwN_wmMibvVSv-Cj2wA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--IOEWtfUOtTcLQCr4b2OSiPoLBdgjXeGnJ
Content-Type: multipart/mixed; boundary="hYzKYepWbPLaMpgeIlqnLbUMcqDP1RkvL";
protected-headers="v1"
From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?=
<jean-sebastien.pedron@dumbbell.fr>
To: freebsd-erlang@freebsd.org
Message-ID: <fa6d6798-3e54-0713-345c-1e8ae2f0c2da@dumbbell.fr>
Subject: Re: Dumb question on erlang ports
References: <CAGipyQ_7Sbwf72QhRmOifH-mSefJsuCWwN_wmMibvVSv-Cj2wA@mail.gmail.com>
In-Reply-To: <CAGipyQ_7Sbwf72QhRmOifH-mSefJsuCWwN_wmMibvVSv-Cj2wA@mail.gmail.com>
--hYzKYepWbPLaMpgeIlqnLbUMcqDP1RkvL
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
On 8/3/18 2:06 PM, John Parkey wrote:
> Hi
Hi!
> Sorry to bother you, but I am coming back to doing some erlang dev work=
on
> freebsd, after a while away.
Great! :)
> I am a bit confused by there being erlang-runtime ports for versions 20=
and
> 21, but the main erlang lang port is at version 19.3. Presumably versi=
on
> 19.3 cannot be used to develop stuff which runs on 21? If not, what is=
the
> rationale for the existence of the later runtimes?
Having all the erlang-runtime-* ports allow use all of them while
working with Erlang as you guessed.
If the main lang/erlang port is still at Erlang 19.x, it's probably
because we need to be 100% sure all services depending on Erlang are
working with newer Erlang releases. I can speak for RabbitMQ for
instance and it took time to add support for Erlang 20 and even more for
Erlang 21.
Back to the development experience (I work on RabbitMQ itself), I use
Erlang 19 as my day-to-day environment. I use erlang-runtime-{20,21} to
test changes with newer versions. I don't have to recompile anything
because the compiled modules are forward-compatible. If the main port is
updated to e.g. Erlang 21, I would have to override $PATH to change the
default back to Erlang 19 or recompile to test + maybe change the code
to not rely on Erlang 21 features.
That said, I agree that the Erlang ports would benefit from FLAVOURS.
--=20
Jean-S=C3=A9bastien P=C3=A9dron
--hYzKYepWbPLaMpgeIlqnLbUMcqDP1RkvL--
--IOEWtfUOtTcLQCr4b2OSiPoLBdgjXeGnJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZwh/0a6uDhLbxqbwOemXYaX9lMwFAltkZBkACgkQOemXYaX9
lMxKghAAzO3vResD5CJbetN8/reULdBz5EmSIBVp3zIeyU2wJSd5MYuJr1KRWyEC
08KCkNoJ/ZJM+asCM0aB9Wth7s1BfF6In7kT8WdPMpX4Woiv6m7Y94cHRN9UtkvO
t4P0p7s6R+2nPtku4sbIsk1zpwEs3mGFyhZx32PXF8J2qlzbxEtioKgNJHLvu0w9
BTYlbGvEmY99K6vmZOTMM/cO9HLsI53hBxk/uu2lxhSl5sskU3URzfeEv8c6+9pw
nyvq1rRqokk1aJ28AWEFf1qSbyZSN3924y1irrvYlQ3raPT1Ygleqrw7la4Wjc7n
c945RXyfr8YQycoeJ5zkk48r5kJeWkC6IEywfJ0LMiRrYOSCA58nlg9//uuebqRk
k6pO1sxu5GS5FBDvcsaP1BhEITdFhSZhB870MSHMKFfK7QfsvRgFlIhQNSTQ71Tc
sisW1JqPX8S3i5w8ArMUsJZmlkIAEF2S1FqS2ZQNbYSr8CjAGXB3EaxOWJBGkEaV
sbTeZHMJCHtuoc+M9X+7mTEUrzxymd1owXNd/RPFg1cslaiyn/4LxLP5rPeURFyj
skmNtDA91ebYMp84Qp811v07fad8HQ2kcmX5j32bC/jBledp4BZFX7H1FZGJn46Z
8h3yGS3rkY/9xh278+OMjTLME0/RNdjec5DB646BYeMqyUxO/KM=
=nc3r
-----END PGP SIGNATURE-----
--IOEWtfUOtTcLQCr4b2OSiPoLBdgjXeGnJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fa6d6798-3e54-0713-345c-1e8ae2f0c2da>