Skip to content

Commit 063f872

Browse files
authored
nix-store-layer: Cut stabilization in future work down
Can just refer to NixOS#136 now.
1 parent ec44f73 commit 063f872

File tree

1 file changed

+2
-19
lines changed

1 file changed

+2
-19
lines changed

rfcs/0134-nix-store-layer.md

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -253,22 +253,5 @@ A new store team, per the above, could lead the process from our end, since the
253253
## Stabilization
254254

255255
There is a looming question on how to stabilize Nix's big backlog of unstable features (New CLI, Flakes).
256-
There is a lot of bad-blood over Flakes, both the feature itself and the way it has been rolled out.
257-
I think the stabilization process can be an opportunity to heal old wounds.
258-
259-
At a minimum, this can involve stabilizing the new CLI before Flakes.
260-
But even that that is a lot of new feature surface area to review.
261-
I think even better is stabilizing just the store-only new CLI first.
262-
263-
This is easily the least controversial part of our unstable feature backlog, and yet there is still plenty to discuss.
264-
Questions like
265-
266-
- logging
267-
- store paths on `stdout` at end of build?
268-
- Should commands like `show-derivation` should use `--json` by default
269-
- Flat vs hierarchical commands
270-
- is `--derivation` a good flag? (I think not!)
271-
272-
are all in-scope.
273-
274-
Having a conversation just on this narrow first batch of stabilization both builds trust, and ensures these still-important issues they aren't lost in flame wars over more divisive topics.
256+
[RFC 136](https://github.com/NixOS/rfcs/pull/136) is a plan on how to stabilize these features that greatly leverages this.
257+
See it for further details.

0 commit comments

Comments
 (0)