Bug 245230 - [exp-run] lang/elixir: update to 1.10.2
Summary: [exp-run] lang/elixir: update to 1.10.2
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Port Management Team
Depends on:
Reported: 2020-04-01 11:58 UTC by Dave Cottlehuber
Modified: 2020-04-21 16:59 UTC (History)
1 user (show)

See Also:
dch: maintainer-feedback+
dch: exp-run?

elixir_patch_v1 (13.16 KB, patch)
2020-04-01 11:58 UTC, Dave Cottlehuber
dch: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Dave Cottlehuber freebsd_committer 2020-04-08 09:47:33 UTC
added + from erlang@
Comment 4 Dave Cottlehuber freebsd_committer 2020-04-20 19:10:53 UTC
thanks Antoine. I was expecting that we'd see more than just a single port failure here, and that we could get an exprun that covers more than just 11.3R, which I can do locally.

What's the normal scope for an exp-run? Can it be done to continue even after first port failure?
Comment 5 Antoine Brodin freebsd_committer 2020-04-20 19:15:49 UTC
(In reply to Dave Cottlehuber from comment #4)
I believe that on 12.1 the new failures were the same as on 11.3
Comment 6 Mark Felder freebsd_committer 2020-04-21 14:26:42 UTC
> ** (Mix) You're trying to run :rabbitmqctl on Elixir v1.10.2 but it has declared in its mix.exs file it supports only Elixir >= 1.7.0 and < 1.10.0

Can someone running rabbitmq just patch their port locally to lift this restriction and verify things still work? I suspect this is just rabbitmq being overly cautious.
Comment 7 Dave Cottlehuber freebsd_committer 2020-04-21 16:59:56 UTC
wrt rabbitmq, see r532229 this was already addressed in 3.8.3 upstream.

I plan to remove the 4 remaining ports as they have not worked in ages:

- databases/elixir-mongo
- databases/elixir-exredis
- devel/elixir-bson
- devel/elixir-tirexs

I personally see little value of having elixir & erlang libraries directly
in the tree, unless they have C dependencies (NIFs) or port drivers. I
know very few people who distribute BEAM applications without a release
these days.