{ lib }: /** Usage: You define you custom builder script by adding all build steps to a list. for example: builder = writeScript "fsg-4.4-builder" (textClosure [doUnpack addInputs preBuild doMake installPhase doForceShare]); a step is defined by noDepEntry, fullDepEntry or packEntry. To ensure that prerequisite are met those are added before the task itself by textClosureDupList. Duplicated items are removed again. See trace/nixpkgs/trunk/pkgs/top-level/builder-defs.nix for some predefined build steps Attention: let pkgs = (import ) {}; in let inherit (pkgs.stringsWithDeps) fullDepEntry packEntry noDepEntry textClosureMap; inherit (pkgs.lib) id; nameA = noDepEntry "Text a"; nameB = fullDepEntry "Text b" ["nameA"]; nameC = fullDepEntry "Text c" ["nameA"]; stages = { nameHeader = noDepEntry "#! /bin/sh \n"; inherit nameA nameB nameC; }; in textClosureMap id stages [ "nameHeader" "nameA" "nameB" "nameC" nameC # <- added twice. add a dep entry if you know that it will be added once only [1] "nameB" # <- this will not be added again because the attr name (reference) is used ] # result: Str("#! /bin/sh \n\nText a\nText b\nText c\nText c",[]) [1] maybe this behaviour should be removed to keep things simple (?) */ let inherit (lib) concatStringsSep head isAttrs listToAttrs tail ; in rec { /** Topologically sort a collection of dependent strings. Only the values to keys listed in `arg` and their dependencies will be included in the result. ::: {.note} This function doesn't formally fulfill the definition of topological sorting, but it's good enough for our purposes in Nixpkgs. ::: # Inputs `predefined` (attribute set) : strings with annotated dependencies (strings or attribute set) A value can be a simple string if it has no dependencies. Otherwise, is can be an attribute set with the following attributes: - `deps` (list of strings) - `text` (Any `arg` (list of strings) : Keys for which the values in the dependency closure will be included in the result # Type ``` textClosureList :: { ${phase} :: { deps :: [String]; text :: String; } | String; } -> [String] -> [String] ``` # Examples :::{.example} ## `lib.stringsWithDeps.textClosureList` usage example ```nix textClosureList { a = { deps = [ "b" "c" "e" ]; text = "a: depends on b, c and e"; }; b = { deps = [ ]; text = "b: no dependencies"; }; c = { deps = [ "b" ]; text = "c: depends on b"; }; d = { deps = [ "c" ]; text = "d: not being depended on by anything in `arg`"; }; e = { deps = [ "c" ]; text = "e: depends on c, depended on by a, not in `arg`"; }; } [ "a" "b" "c" ] => [ "b: no dependencies" "c: depends on b" "e: depends on c, depended on by a, not in `arg`" "a: depends on b, c and e" ] ``` ::: Common real world usages are: - Ordering the dependent phases of `system.activationScripts` - Ordering the dependent phases of `system.userActivationScripts` For further examples see: [NixOS activation script](https://nixos.org/manual/nixos/stable/#sec-activation-script) */ textClosureList = predefined: arg: let f = done: todo: if todo == [ ] then { result = [ ]; inherit done; } else let entry = head todo; in if isAttrs entry then let x = f done entry.deps; y = f x.done (tail todo); in { result = x.result ++ [ entry.text ] ++ y.result; done = y.done; } else if done ? ${entry} then f done (tail todo) else f ( done // listToAttrs [ { name = entry; value = 1; } ] ) ([ predefined.${entry} ] ++ tail todo); in (f { } arg).result; textClosureMap = f: predefined: names: concatStringsSep "\n" (map f (textClosureList predefined names)); noDepEntry = text: { inherit text; deps = [ ]; }; fullDepEntry = text: deps: { inherit text deps; }; packEntry = deps: { inherit deps; text = ""; }; stringAfter = deps: text: { inherit text deps; }; }