* Include the system type in manifests as a hint for the

Dependencies

• [2] TPDJL4TY * Add derivations and all build-time dependencies of a build to the
• [3] MVB7RRLT * Move NARs from the NixChannel controller to the Root controller and
• [4] 6US6LEC7 * Add a NarSize field to Hydra manifests. This allows nix-env
• [5] BHZXGT2H * Channels: provide an index page that lists all the packages in the
• [6] 7UJ5YV4V * Provide a channel for each project containing all the latest
• [7] SJN2QPWH * Big speed-up of the job status page and the channel generation (such
• [8] FM4O2L4M hydra: if evaluator sees cached build, also add the buildproducts
• [*] LBNVQXUB * Build the /build stuff in a separate controller.
• [*] IWVA2P2Y * Generate manifests on demand. Next step: generate NAR archives on
• [*] Y35C6GHH * One-click installs.

Change contents

• replacement in src/lib/Hydra/Helper/CatalystUtils.pm at line 126
  [2.291]→[2.291:338](∅→∅)
  − push @storePaths, $build->outpath;
  [2.291]

  [2.338]
  + push @storePaths, $build->outpath;
• edit in src/lib/Hydra/Helper/CatalystUtils.pm at line 130
  [5.724]

  [5.1178]
  + # Put the system type in the manifest (for top-level paths) as

  + # a hint to the binary patch generator. (It shouldn't try to

  + # generate patches between builds for different systems.) It

  + # would be nice if Nix stored this info for every path but it

  + # doesn't.

  + $c->stash->{systemForPath}->{$build->outpath} = $build->system;
• edit in src/lib/Hydra/View/NixManifest.pm at line 35
  [3.796]

  [12.590]
  +

  + my $system = $c->stash->{systemForPath}->{$path};
• edit in src/lib/Hydra/View/NixManifest.pm at line 46
  [4.251]

  [11.1588]
  + (defined $system ? " System: $system\n" : "") .