Skip to content
/ rfcs Public

Conversation

@roberth
Copy link
Member

@roberth roberth commented Jan 18, 2026

This RFC proposes that stores provide a nix-store.json file declaring their properties, enabling:

  • Discovery of store settings (storeDir, encoding, etc.)
  • Forward compatibility through explicit feature requirements
  • A unified replacement for the ad hoc nix-cache-info format

Rendered: https://github.com/roberth/rfcs/blob/self-describing-store/rfcs/0196-self-describing-store.md

Shepherd nominations welcome!

@roberth roberth changed the title RFC 0196: Start RFC about nix-store.json [RFC 0196]: Self-describing store Jan 18, 2026
@roberth roberth changed the title [RFC 0196]: Self-describing store [RFC 0196] Self-describing store Jan 18, 2026
as well as slightly reduce the number of requests.
The details of such an integration would be decided by those involved with RFC 195.

## Concrete example: the case hack
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm missing two very simple examples, a directory containing NARInfo files and NAR files (with whatever compression), and the one at ../../var/nix/db/nix-store.json.

There's arguably a big difference to storing Nars or unpacked files, and I feel like we're missing some format field of some sort. It doesn't map nicely to the more additive nature of features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants