nixpkgs-suyu/pkgs/development/erlang-modules/default.nix

{ pkgs }: #? import <nixpkgs> {} }:

let
  self = rec {
    hex = import ./hex-packages.nix { callPackage = self.callPackage; };
    callPackage = pkgs.lib.callPackageWith (pkgs // self // hex);

    buildRebar3 = callPackage ./build-rebar3.nix {};
    buildHex = callPackage ./build-hex.nix {};
  };
in self // self.hex
Add few erlang modules 2015-12-10 00:12:37 +01:00			`{ pkgs }: #? import <nixpkgs> {} }:`

			`let`
			`self = rec {`
erlang support: move hex packages to hex namespace This commit moves all the hex based packages to a single namespace. It also moves all the packages to a single file. This is in preparation for the move to a system to generate the hex packages from the hex package store. 2016-01-11 00:11:07 +01:00			`hex = import ./hex-packages.nix { callPackage = self.callPackage; };`
			`callPackage = pkgs.lib.callPackageWith (pkgs // self // hex);`
erlang support: seperate hex and rebar3 support Building Hex packages is a superset of building with rebar3. There is no need to force folks that use rebar3 but not hex to build with hex. This commit seperates the rebar3 specific bits and the hex specific bits into seperate functions that can be used independently. 2016-01-11 00:25:45 +01:00
			`buildRebar3 = callPackage ./build-rebar3.nix {};`
Add few erlang modules 2015-12-10 00:12:37 +01:00			`buildHex = callPackage ./build-hex.nix {};`
			`};`
erlang support: move hex packages to hex namespace This commit moves all the hex based packages to a single namespace. It also moves all the packages to a single file. This is in preparation for the move to a system to generate the hex packages from the hex package store. 2016-01-11 00:11:07 +01:00			`in self // self.hex`