Flakes as Default Interface: NixOS 23.05 Compatibility Boundary Remains Unresolved

Question

Transition UncertaintyNixOS 23.05 ships with Nix 2.13 while the project continues to evaluate whether flakes should become the default user interface. The experimental flag requirement and potential breakage of classic nix-env workflows create a compatibility boundary that affects configuration management strategies.Constraints and Open QuestionsAdopting flakes as default would change the primary interaction model for system configuration and package management. Existing channels-based configurations, imperative nix-env scripts, and documentation referencing legacy commands would require migration. The RFC process remains open, and no target release has been committed for the transition.Flakes remain marked experimental in Nix 2.13, requiring explicit experimental-features = [ \"flakes\" \"nix-command\" ] in nix.conf.Classic nix-env -iA and nix-channel workflows continue to function but lack a formal deprecation timeline.Third-party tooling and CI pipelines often assume the current default interface.What criteria will determine when flakes exit experimental status? Will a migration path be provided for channel-based configurations, or is a clean break expected? How will the project communicate the transition timeline to downstream distributions and tooling maintainers?

Tasadduq Burney · Answer

The transition to flakes as the primary interface for NixOS is currently stalled by the experimental status of the Nix package manager itself. In NixOS 23.05, which utilizes Nix 2.13, flakes remain an experimental feature, creating a functional gap for users choosing between modern declarative workflows and stable legacy channel-based systems.
The 'compatibility boundary' stems from the requirement of explicit opt-in. While flakes offer superior reproducibility via the Flake.lock file, the project has not yet established a deprecation timeline for the nix-channel and nix-env workflows. This leaves configuration management strategies in a state of limbo.

Current State of the Interface Boundary
To use flakes on NixOS 23.05, users must manually bypass the safety locks by configuring:

Experimental Flags: Flakes require experimental-features = [ \"flakes\" \"nix-command\" ] in nix.conf.
  Workflow Divergence: Classic imperative nix-env -iA commands do not natively support flake-based inputs, leading to 'split-brain' configurations if both are used.
  Tooling Lag: Many CI/CD pipelines and third-party scripts rely on the legacy channel-based structure, which may break if flakes become mandatory without a shim.

Criteria for exiting experimental status
The project's decision to remove the 'experimental' tag depends on three primary factors that currently remain unresolved:

API Stability: The flakes API must reach a level of maturity that prevents breaking changes for downstream distributions.
  Tooling Adoption: The ecosystem (build tools, IDE extensions, and CI providers) must demonstrate that flake-native inputs are the standard.
  Migration Path: A clear strategy for converting existing nix-channel configurations to flakes must be provided to prevent community fragmentation.

Until these criteria are met, the safest approach for NixOS 23.05 users is to maintain channel-based configurations for system-level stability while utilizing flakes for isolated project-level development to ensure reproducibility.

Flakes as Default Interface: NixOS 23.05 Compatibility Boundary Remains Unresolved

Transition Uncertainty

Constraints and Open Questions

1 answer

Current State of the Interface Boundary

Criteria for exiting experimental status

Your perspective belongs here.

0 question comments