The FreeBSD Erlang Team

Erlang, Elixir, rebar, relx, and related stuff.

Our mailing list is erlang@.

A #freebsd-erlang channel is available on freenode.

• Dave Cottlehuber (dch@)
• Babak Farrokhi (farrokhi@)
• Jimmy Olgeni (olgeni@)
• Jean Sébastien Pédron (dumbbell@)
• Kenji Rikitake
• Ashish Shukla (ashish@)
• You are welcome to join :)

• Create port for Erlang Corba tools (Erlang 21)
• Unbreak ODBC support (currently not building because of some issue with #includes)
• Make sure Erlang ports are compatible with openssl-devel and libressl
• Make Erlang ports buildable from GitHub sources (remove patching and prebuilt tarballs)
• Make lang/erlang-doc buildable from GitHub sources (is it worth it? depends on Apache FOP at least)
• Automatically generate plist for Erlang library ports (required for flavors)
• Add support for flavors (Erlang 19, 20, 21)
• Install library ports in a separate directory (with major version number) and change ERL_LIBS for application ports that require them
• Generalize the dependency loading mechanism of devel/rebar3 (or even better databases/leofs) and make it available to all ports

• Install RabbitMQ code in a separate directory, like CouchDB does
• Check and commit databases/couchdb2 port PR 218844
• New port: DalmatinerDB (started here)
• New port: BarrelDB
• New port: VerneMQ
• Make a separate erlang-epmd port + rc.d daemon to allow ports to rely on a parent epmd daemon starting with reduced privileges PR213001

• Rebar3 insists on downloading a package index even if all dependencies were already provided (see devel/relx for cache file handling)

• Do Erlang library ports even make sense? (probably not so much - compare with Go situation)
• What's the status of upstream Riak?