~evhan/beaker

9397e14dc0776b7a1508cae58880b129695e94b3 — Evan Hanson 9 months ago 48447ae
Small documentation updates for Nix helpers
1 files changed, 9 insertions(+), 5 deletions(-)

M nix.md
M nix.md => nix.md +9 -5
@@ 23,7 23,11 @@ to pull into scope, for example:

You can use a specific version of the Nix packages collection by setting the
`pkgs` property in the import statement. By default, the `<nixpkgs>` path is
used.
used:

    with import (fetchTarball https://git.sr.ht/~evhan/beaker/archive/master.tar.gz) {
      pkgs = import <nixpkgs-unstable> {};
    };

=== Fetching Egg Dependencies



@@ 123,10 127,10 @@ the same attributes as `eggRepository`.

Unlike `eggRepository`, this derivation only preserves shared object files in
the repository path, and it does not expose the output repository to
downstream derivations. This means that all `egg-info`, `inline` and `link`
files are removed, making the result unsuitable for use in the `builtInputs`
of another `eggProgram`. It should only be used to create executables, not
extension repositories.
downstream derivations. This means that all `egg-info`, `inline`, `link` and
`types` files are removed, and the result is unsuitable for use in the
`builtInputs` of another `eggProgram`. It should only be used to produce
executables, not extension repositories intended for reuse.

Combining the `eggRepository` and `eggProgram` derivations is useful to stage
build operations, for example to avoid rebuilding all egg dependencies