From Fedora Project Wiki
(Created page with ''''THIS DOCUMENT IS WIP''' This document seeks to document the conventions and customs surrounding the proper packaging of Erlang modules and applications in Fedora and EPEL. It...')
 
No edit summary
Line 14: Line 14:


Erlang package should not install its original sources. Instead packages should ensure that it's built with +debug_info flag. It does NOT impact the runtime performance of the application at all (beam loader disregards debug symbols before loading to VM). Dialyzer requires either debug info or original sources.
Erlang package should not install its original sources. Instead packages should ensure that it's built with +debug_info flag. It does NOT impact the runtime performance of the application at all (beam loader disregards debug symbols before loading to VM). Dialyzer requires either debug info or original sources.
[[Category:Packaging guidelines]]

Revision as of 19:25, 20 October 2010

THIS DOCUMENT IS WIP

This document seeks to document the conventions and customs surrounding the proper packaging of Erlang modules and applications in Fedora and EPEL. It does not intend to cover all situations, but to codify those practices which have served the Fedora Erlang community well.

Naming

erlang-%{realname}

File Locations

Erlang packages should install theirselves to %{_libdir}/erlang/lib/%{realname}-%{version}. Big applications, such as ejabberd or rabbitmq-server install their content somewhere else due to historical reasons.

Debug symbols / source installation / dialyzer

Erlang package should not install its original sources. Instead packages should ensure that it's built with +debug_info flag. It does NOT impact the runtime performance of the application at all (beam loader disregards debug symbols before loading to VM). Dialyzer requires either debug info or original sources.