News for hackers. Stuff that matters.
Re:Nixery – Docker images on the fly with Nix by chriswarbo on Tuesday April 19, 2022 @12:07PM (#31085039)
> Either way, I would just drop the resulting binary in /usr/bin and it's done. With Nix... I'm totally stumped.

If you don't care about Nixpkgs conventions ("build phases", etc.) then you can use `runCommand` to run arbitrary bash code. It's a function which takes three arguments: a name for the output, a key/value mapping for the environment variables (plus a few some special names), and a string of bash code (usually written between ''two single quotes'').

    with import <nixpkgs> {};
    runCommand
      "my-favourite-program"  # A name for the output
      {
        # A key/value mapping of env vars
        myVar = "myValue";

        # The 'buildInputs' name is special: for each element 'x', the directory '${x}/bin'
        # will be appended to the PATH env var
        buildInputs = [ jq gcc ];
      }
      ''
        # This is a multi-line string containing arbitrary bash code.
        # The output path will be provided via the env var $out so we
        # just need to create a file or folder with that path
        mkdir -p "$out/bin"
        echo "$myVar" > "$out/bin/my-executable"
        chmod +x "$out/bin/my-executable"
      ''
One complication is that (by default) the script will be run in a sandbox, with no network access. We should fetch anything it depends on up-front, using e.g. fetchurl, fetchGit, etc. Here's a more realistic example:

    with import <nixpkgs> {};
    runCommand "foo"
      {
        release = fetchurl {
          url = "http://example.com/foo/foo-1.0.zip";
          hash = "sha256-iqZDwWkQA9XMTICEMCt5xDlmfmiIwzpeE3HJLbgbDXs=";
        };
        buildInputs = [ unzip ];
      }
      ''
        unzip "$release"
        mkdir -p "$out/bin"
        mv foo-1.0/binary "$out/bin/foo"
      ''

There are no comments on this comment yet.