aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorDave Cottlehuber <dch@FreeBSD.org>2022-06-28 06:28:39 +0000
committerDave Cottlehuber <dch@FreeBSD.org>2022-06-28 06:32:30 +0000
commitab4964e6d96e9d3ac2c75c414dee85bf625a06fa (patch)
tree8f06b6af0be8a6ae2d439a6e2a07231237ed5619 /UPDATING
parent7354d338c87180a19fc6fcee01b9ceb95cf916ea (diff)
downloadports-ab4964e6d96e9d3ac2c75c414dee85bf625a06fa.tar.gz
ports-ab4964e6d96e9d3ac2c75c414dee85bf625a06fa.zip
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING21
1 files changed, 21 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 01ea8a799abb..9e1dc3faf14d 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,27 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20220628:
+ AFFECTS: users of Erlang and Elixir
+ AUTHOR: dch@FreeBSD.org
+
+ For more than a decade, the Elixir Mix tool and the Erlang rebar
+ or erlang.mk build tools have been the defacto way of installing
+ and managing packages for specific applications.
+
+ All main-stream applications, from Riak, CouchDB, RabbitMQ, Phoenix,
+ and Elixir, expect that packages are fetched and compiled into an OTP
+ Release, with in-built version locking, external package management.
+
+ There is no point in maintaining a large number of libraries, that
+ are used neither for development, nor operations.
+
+ Users are directed to https://rebar3.org/ https://erlang.mk/ or
+ https://elixir-lang.org/getting-started/mix-otp/introduction-to-mix.html
+ to fetch custom packages.
+
+ https://www.freebsd.org/status/report-2021-07-2021-09/#_freebsd_erlang_ecosystem_ports_update
+
20220626:
AFFECTS: users of python
AUTHOR: thierry@FreeBSD.org