Opened 9 years ago
Closed 9 years ago
#48708 closed defect (fixed)
elixir 1.0.5 not compatible with erlang 18
Reported by: | rlonstein@… | Owned by: | ci42 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | milmazz (Milton Mazzarri) | |
Port: | elixir erlang |
Description
See https://github.com/jeremyjh/dialyxir/issues/26 and https://github.com/elixir-lang/elixir/issues/3212.
Can we version erlang into erlang17 and erlang18 and update this portfile to depend on erlang17 until the elixir 1.2 release.
Change History (3)
comment:1 follow-up: 2 Changed 9 years ago by Ionic (Mihai Moldovan)
Cc: | me@… added; ciserlohn removed |
---|---|
Keywords: | erlang elixir removed |
Owner: | changed from macports-tickets@… to ciserlohn@… |
Port: | elixir erlang added; lang:elixir removed |
comment:2 Changed 9 years ago by rlonstein@…
Replying to ionic@…:
Please don't add random keywords. Thanks for CC'ing the maintainer, but note that the CC field takes a full email address only.
I'll assign the ticket to the
erlang
maintainer and addelixir
's maintainer as a CC. I'd rather see elixir fixed than an old version be created just for one port.
There's no due date for the upstream elixir 1.1.0 and therefore no due date for the following release 1.2.0 based on it which will support Erlang 18. Leaving it like this results in a broken elixir port until an unknown future date.
Please don't add random keywords. Thanks for CC'ing the maintainer, but note that the CC field takes a full email address only.
I'll assign the ticket to the
erlang
maintainer and addelixir
's maintainer as a CC. I'd rather see elixir fixed than an old version be created just for one port.