nixpkgs/pkgs/development/beam-modules/build-hex.nix

{ lib, stdenv, buildRebar3, fetchHex }:

{ name, version, sha256
, builder ? buildRebar3
, hexPkg ? name
, ... }@attrs:

with lib;

let
  pkg = self: builder (attrs // {

    src = fetchHex {
      pkg = hexPkg;
      inherit version;
      inherit sha256;
    };
  });
in
  fix pkg
pkgs/development: stdenv.lib -> lib 2021-01-23 17:15:07 +00:00			`{ lib, stdenv, buildRebar3, fetchHex }:`
Add few erlang modules 2015-12-09 23:12:37 +00:00
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-10 23:25:45 +00:00			`{ name, version, sha256`
erlang: refactor: build packages per Erlang/OTP. This change introduces a fixpoint, which allows to do deep override when building packages defined in pkgs/development/beam-modules/default.hex. This allows to provide beam.packages.erlang{,R16,R17,R18,R19} which contains the same packages built with different Erlang/OTP versions. Top-level attribute beamPackages points at beam.packages.erlangR18, the same applies to other top-level Erlang packages. TODO: - beam.packages.erlang{R16,R17} is almost useless, since rebar/rebar3 does not build using these versions; - all packages in beam.packages which use buildMix are actually built with erlangR18; - update documentation. 2017-06-17 15:28:41 +01:00			`, builder ? buildRebar3`
Add support for Hex package name There are some packages on Hex which have custom hex-specific names, but inside there's a base project name. Remove most packages andadd ibrowse, meck, jiffy 2015-12-10 20:39:13 +00:00			`, hexPkg ? name`
Add few erlang modules 2015-12-09 23:12:37 +00:00			`, ... }@attrs:`

pkgs/development: stdenv.lib -> lib 2021-01-23 17:15:07 +00:00			`with lib;`
Add few erlang modules 2015-12-09 23:12:37 +00:00
Add shell env to buildHex packages. This adds erlangPackages.${name}.env, which is usable to launch a shell with the package and it's dependencies like this: nix-shell -A erlangPackages.lager.env This required: 1) refactoring buildHex to become a fixed-point function, 2) moves output of a package into $out/${name}, 3) introduces erlEnv (buildEnv, which links in package and it's deps into one directory - a super-simple plagiarization of haskellPackages.compiler.ghcWithPackages) and 4) shell function producing a un-buildable derivation to be used by nix-shell 2015-12-18 22:51:51 +00:00			`let`
erlang: refactor: build packages per Erlang/OTP. This change introduces a fixpoint, which allows to do deep override when building packages defined in pkgs/development/beam-modules/default.hex. This allows to provide beam.packages.erlang{,R16,R17,R18,R19} which contains the same packages built with different Erlang/OTP versions. Top-level attribute beamPackages points at beam.packages.erlangR18, the same applies to other top-level Erlang packages. TODO: - beam.packages.erlang{R16,R17} is almost useless, since rebar/rebar3 does not build using these versions; - all packages in beam.packages which use buildMix are actually built with erlangR18; - update documentation. 2017-06-17 15:28:41 +01:00			`pkg = self: builder (attrs // {`
erlang support: allow nix-shell to work correctly This changes build-hex.nix so that the buildHex and related functions work correctly in a nix-shell. 2016-01-10 22:48:44 +00:00
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-10 23:25:45 +00:00			`src = fetchHex {`
Add shell env to buildHex packages. This adds erlangPackages.${name}.env, which is usable to launch a shell with the package and it's dependencies like this: nix-shell -A erlangPackages.lager.env This required: 1) refactoring buildHex to become a fixed-point function, 2) moves output of a package into $out/${name}, 3) introduces erlEnv (buildEnv, which links in package and it's deps into one directory - a super-simple plagiarization of haskellPackages.compiler.ghcWithPackages) and 4) shell function producing a un-buildable derivation to be used by nix-shell 2015-12-18 22:51:51 +00:00			`pkg = hexPkg;`
			`inherit version;`
			`inherit sha256;`
			`};`
			`});`
			`in`
			`fix pkg`