FS#54776 - [elixir] split into elixir and elixir-nox
Attached to Project:
Community Packages
Opened by Magnus Müller (evnu) - Wednesday, 12 July 2017, 12:27 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:07 GMT
Opened by Magnus Müller (evnu) - Wednesday, 12 July 2017, 12:27 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:07 GMT
|
Details
Description:
Erlang is split into erlang and erlang-nox. Currently, elixir depends on erlang-nox, which is surprising. If a user installs elixir (without manually installing erlang) and tries to run the observer using :oberver.start(), a less-than-helpful error message comes up: iex(1)> :observer.start() 14:12:30.596 [error] ERROR: Could not find 'wxe_driver.so' in: /usr/lib/erlang/lib/wx-1.8.1/priv {:error, {{:load_driver, 'No driver found'}, [{:wxe_server, :start, 1, [file: 'wxe_server.erl', line: 65]}, {:wx, :new, 1, [file: 'wx.erl', line: 115]}, {:observer_wx, :init, 1, [file: 'observer_wx.erl', line: 98]}, {:wx_object, :init_it, 6, [file: 'wx_object.erl', line: 372]}, {:proc_lib, :init_p_do_apply, 3, [file: 'proc_lib.erl', line: 247]}]}} This message is caused by erlang-nox, as wx support is not present in that package. Additional info: * elixir 1.4.5-1 Steps to reproduce: |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:07 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/elixir/issues/1
Saturday, 25 November 2023, 20:07 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/elixir/issues/1
Elixir itself does not behave differently either way.
I think depending on erlang or erlang-nox is the better way, as thats where the actual behaviour changes.
I do have the feeling though, that this is something that needs to be changed in the erlang packages. As I do understand the process, they need to "provide" a "erlang-environment" elixir can then depend on.
This will not affect other software (as far as I understood it), since they can still depend on the original "erlang" and "erlang-nox" packages until they pick up the new architecture.
But I am not quite sure if I understand it correctly, therefore I'd be happy if someone more knowledgable could chime in and start the proper process to change packaging appropriately.
PS: To avoid installing the package "erlang" as explicit, I do install elixir in a two step manor:
# pacman -S --asdep erlang
# pacman -S elixir
This works since "erlang" "provides" "erlang-nox", and especially important, this will properly mark "erlang" as orphan as soon as one removes "elixir".