Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AArch64 packages #88

Closed
hrw opened this issue Nov 7, 2019 · 3 comments
Closed

AArch64 packages #88

hrw opened this issue Nov 7, 2019 · 3 comments
Labels

Comments

@hrw
Copy link
Contributor

hrw commented Nov 7, 2019

While RabbitMQ is architecture agnostic Erlang is not. So newer version of RabbitMQ are not usable on !x86 architectures.

Please provide AArch64 packages so we can deploy OpenStack on our servers with something fresher than 3.7.10 (last ver working with CentOS 7 Erlang).

@michaelklishin
Copy link
Member

michaelklishin commented Nov 7, 2019

I'm afraid our team never intended to be the leader in Erlang packaging, so we very likely won't be covering ARM architectures unless there is a trivial way to cross-compile.

You have a few options:

  • Use kerl to build from source
  • Use this open source package and adapt it for ARM64
  • Reach out to Erlang Solutions about ARM64 packages
  • Ask on the Erlang mailing list for more options

Note that the Erlang/OTP team at Ericsson would not be interested in packaging improvements. In our experience, they believe that packaging is something for the community to worry about, which is why we have given up and decided to build Erlang packages for two most popular distribution families and one most popular architecture.

@hrw
Copy link
Contributor Author

hrw commented Nov 7, 2019

Thanks. Will take a look at how your scripts work and in worst case create own repo.

@michaelklishin
Copy link
Member

I chatted with @gerhard and he suggested a couple more things. You can look into deploying RabbitMQ in containers. We already have a fairly mature image which the community maintains, and it is updated within 24 hours when a new RabbitMQ, Erlang or OpenSSL versions come out.

For us to produce an ARM64 package would require adding an ARM64 Concourse worker which would not be used for anything else. Currently, there isn't enough demand to justify it, even though we would like to make the latest Erlang version availability a solved problem, we have to focus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants