Info

• Milestone
• RFC 92: dynamic derivations
• PR thread

Steps

Here are the PRs to review:

Preparatory work

1. Low level <drvPath>^<outputName> installable syntax to match existing <highLevelInstallable>^<outputNames> syntax  #4543
   • OutputSpec for DerivationGoal and DerivedPath, today's OutputSpec -> ExtendedOutputSpec #6815
2. Parse string context elements properly #7543
3. Get rid of .drv special-casing for store path installable #7600
4. Introduce StoreReferences and ContentAddressWithReferences #3746
5. Derivations can output "text-hashed" data #3959
   • Maybe also exportReferencesGraph should build onlydrvs when used with unsafeDiscardOutputsDependency #7339
6. Make more string values work as installables #7601
7. Give queryPartialDerivationOutputMap an evalStore parameter #8724
8. Test and begin documentation of the ATerm format for derivations #8927
9. Improve derivation parsing #8938

Actual implementation

1. Upgrade downstreamPlaceholder to a type with methods #8353
2. Make the Derived Path family of types inductive for dynamic derivations #8369
3. Create (experimental) outputOf primop. #8813
4. Dynamic derivations RFC 92 #4628
5. Revert "Revert "Adapt scheduler to work with dynamic derivations #9415

• A very restricted recursive nix socket in the sandbox #8602
  • Enable a restricted recursive store daemon even when recursive Nix feature is not enabled
  • for adding dependency sources and dependency derivations to the generated derivation

Quality of life / Nice to have

• Support the recursive store in fetchClosure
  • for dependencies on already-evaluated derivations or derivation outputs
• Deep resolutions for dynamic derivations #8947
• document deriver relation non-interaction

CC @tomberek