Packages FAQ

Frequently Asked Questions

  1. Why do you provide packages?
  2. What cost is involved?
  3. Will you build a package for system X for me?
  4. Which environments and platforms are supported?
  5. Is there any support for the packages?
  6. How are the packages built?
  7. What is included in the packages?
  8. I'm having trouble building from source, can you help?
  9. Have the packages been tested?
  10. I need a package for an older Erlang version, can you build it?
  11. Which operating system version is the package compatible with?
  12. How do I install the RPM packages using your public key?
  13. What configurations do you use?

 

1. Why do you provide packages?

We’ve seen that many of our customers have had problems building Erlang on target machines. By providing packages, we are providing a service them, as well as to the community. By using our these ready-to-install packages, you can sidestep spending the time and frustration that is sometimes involved in building it yourself. We hope that this will get more people to use Erlang, and make it easier to adopt the new technology and language.

Back to the list of questions

2. What cost is involved

Packages for the most common operating systems are free of charge. If you need support or have critical bugs that need fixing, we offer three different Support packages that might suit your needs. To enquire about support, go to the Enquiries page, select Support, and fill in the enquiry form.

Back to the list of questions

3. Will you build a package for system X for me?

Yes, we have the infrastructure to do this, although there might be a charge involved. Once Erlang has been ported to a particular operating system and hardware configuration, we can provide Continuous Integration builds for that configuration as part of our Support offering.

 

We are already building for a wide variety of operating systems, and we are continuously adding more. On the Download Erlang Packages page you can see a list of existing packages, as well as list of operating systems that we have lined up on the Download Erlang OTP page.

 

Back to the list of questions

4. Which environments and platforms are supported?

Visit the Packages page for details, as well as the Supported Environments page.

 

Back to the list of questions

5. Is there any support for the packages?

Yes there is. We offer consultative support as well as basic, business and enterprise support. We also offer 24/7 customised support for your applications, as well as other open source projects that are not part of the main distribution, including the Disco project and ejabberd. See the Support page for more details.

Back to the list of questions

6. How are the packages built?

We use the Erlang/OTP team‘s open-source repository when building the packages. They are automatically built by our continuous integration system, Moebius.

When we generate the packages, we also generate the test suite for the various operating systems and run the tests. We make the results visible in HTML format, so you can actually see the quality of the package. Links to the test results are listed with the package download links.

Back to the list of questions

7. What is included in the packages?

We make it our objective to include as much of Erlang/OTP in our packages as possible. For each operating system we aim to include every application, although some packages are missing the support for particular applications.

In the test results you can see which applications have been included. For example, the default CentOS package doesn't include the wx, odbc or crypto applications. However, if the rpmforge repository is included, the package will be complete.

Back to the list of questions

8. I'm having trouble building from source, can you help?

Contact our Sales team, who will help you to set up a Support contract. You can also email the erlang-questions mailing list, or post to the Trapexit forums or Stack Overflow.

Back to the list of questions

9. Have the packages been tested?

Yes; the test results can be viewed online and are linked in package download page – see Download Erlang OTP. We run different tests based on the operating system and hardware configuration.

When you download a package, please check the test results to see whether there were tests that failed, or tests that were skipped, for any of the applications that you plan to use. Please also note that we are constantly working to improve both the packages and the tests.

Back to the list of questions

10. I need a package for an older Erlang version, can you build it?

Yes, we can as part of our Support offering. Please contact our Sales team.

Back to the list of questions

11. Which operating system version is the package compatible with?

Visit the Download Erlang OTP page, where you can see the platform version on which we built the package.

Please Note: you can filter on the operating system type.

Back to the list of questions

12. How do I install the RPM packages using your public key?

First download our public key: ESL-gpg-public

Then, as the root user, issue the following command: rpm --import ESL-gpg-public

Following that, you should be able to install the packages using the normal method supported by your operating system.

Back to the list of questions

13. What configurations do you use?

We use the default configuration after autoconf, with the --enable-hipe flag.

Back to the list of questions