Hi, I would like to ask a build of erlang-rebar for EPEL 8. Would you mind requesting the branches and build them? Thank you very much. - Breno
Upstream rebar2 is dead and has been superseeded by rebar3: I would like to avoid packaging rebar2 to EPEL8 if possible. That said, most Fedora Erlang packaging still use rebar2...
it seems that erlang-rebar2 is a requirement even to build rebar3. e.g. erlang-rebar3 => erlang-certifi => erlang-rebar. in that case, we will need rebar2 in EPEL 8 anyways. is that correct?
We plan to phase out rebar2 and rebuild all the erlang packages with rebar3, but none of us (Erlang SIG) had much time over the last six months. Now that rebar3 is in Fedora, the next step is to update the RPM packaging macros to use rebar3 instead of rebar2. I do not want to push rebar2 to EPEL8 as it already is EOL.
Hi Timothée. Thanks for the feedback. Please, let me know if can help somehow. I am in the packagers group.
Just a FYI, this package is a dependency for elixir. And elixir is a dependency for a couple of packages, ie rabbitmq-server.
Hello, Any updates regarding this? I see many erlang packages built for EL8 now. Thanks.
Given none of the Erlang SIG had obviously much time over the last year, I wonder if erlang-rebar 2.x could be used at least for bootstrap (and rebase it later to erlang-rebar3, like in Fedora)?
That's a good idea. Can we do this?
I am going to be spending some time on this and other interconnected issues. We need to cut over to rebar3 in fedora sooner than later, because upstream erlang has changed how things get linked with erl_interface, and rebar2 doesn't know how to handle it. We probably could hack it together by overriding linker flags, but I'd rather not keep it on life support any longer. rebar3 can handle this properly out of the box. As an example of this, see erlang-sd_notify which is currently FTBFS with erlang 23.x and rebar2 - https://bugzilla.redhat.com/show_bug.cgi?id=1863513 I'm almost positive we can bootstrap rebar3 without rebar2 in EPEL-8. I'm currently in the middle of doing the exact same exercise downstream for OpenStack on RHEL8, and once I get the order of operations worked out we can reapply the same procedure on EPEL8. Actually now that I write it out, it would make more sense to just do it in EPEL8 first.
Thanks a lot for doing this, John. Let us know if you need help testing or something else.
Hi John, Do you have news regarding this? I was checking and appears to me that elixir still uses rebar2 in Fedora rawhide [1]. If that's the case, maybe for now we could just be following whatever fedora is doing and change it along with Fedora in the future. What do you think? 1 https://src.fedoraproject.org/rpms/elixir/blob/rawhide/f/elixir.spec