nix: isolate dev inputs in partitions.dev so consumers only fetch what they need #162

Merged

natsukium merged 3 commits from nix/partition-dev-inputs into main 2026-09-06 21:20:04 +09:00

Conversation 0 Commits 3 Files changed 12 +587 -519

natsukium commented 2026-09-06 13:15:11 +09:00

Owner

Copy link

Nix evaluates every flake input even when only packages/overlays are needed, so nix run and downstream consumers were fetching rust-overlay, treefmt-nix, git-hooks, and home-manager which are only needed for dev shells, checks, and formatting.

• Move those inputs to dev/flake.nix and expose them via flake-parts partitions.dev (extraInputsFlake). Root flake.nix now declares only nixpkgs, flake-parts, and crane.
• Follow the root nixpkgs pin as nixpkgs-dev in the dev flake to avoid revision skew; route checks/devShells/formatter back via partitionedAttrs so nix develop, nix fmt, and nix flake check keep working without workflow changes.
• Keep nix build .#felis and downstream flake.lock free of dev-only nodes (verified with a filtered consumer lock). Docs and skill references updated from flake.nix to dev/flake-module.nix where appropriate.

Verification: nix flake show unchanged, nix build .#felis and nix flake check (including msrv/home-manager-module/pre-commit/treefmt) pass, and an isolated fetch test with broken dev URLs still builds the package.

Nix evaluates every flake input even when only `packages`/`overlays` are needed, so `nix run` and downstream consumers were fetching `rust-overlay`, `treefmt-nix`, `git-hooks`, and `home-manager` which are only needed for dev shells, checks, and formatting. - Move those inputs to `dev/flake.nix` and expose them via `flake-parts` `partitions.dev` (`extraInputsFlake`). Root `flake.nix` now declares only `nixpkgs`, `flake-parts`, and `crane`. - Follow the root `nixpkgs` pin as `nixpkgs-dev` in the dev flake to avoid revision skew; route `checks`/`devShells`/`formatter` back via `partitionedAttrs` so `nix develop`, `nix fmt`, and `nix flake check` keep working without workflow changes. - Keep `nix build .#felis` and downstream `flake.lock` free of dev-only nodes (verified with a filtered consumer lock). Docs and skill references updated from `flake.nix` to `dev/flake-module.nix` where appropriate. Verification: `nix flake show` unchanged, `nix build .#felis` and `nix flake check` (including `msrv`/`home-manager-module`/`pre-commit`/`treefmt`) pass, and an isolated fetch test with broken dev URLs still builds the package.

natsukium added 1 commit 2026-09-06 13:15:11 +09:00

nix: isolate dev inputs in partitions.dev so consumers only fetch what they need ... ed030e7f21

Nix fetches every flake input even when only packages and overlays
are evaluated, so users running nix run or adding felis as a flake
input paid for rust-overlay, treefmt-nix, git-hooks, and home-manager
which are only needed for dev shells, checks, and formatting.

Move those inputs to dev/flake.nix and expose them through
flake-parts partitions.dev via extraInputsFlake. The root flake now
declares only nixpkgs, flake-parts, and crane, so downstream locks
no longer include dev-only nodes. The dev partition follows the root
nixpkgs pin as nixpkgs-dev to avoid revision skew, and
partitionedAttrs routes checks, devShells, and formatter back to root
so nix develop, nix fmt, and nix flake check keep working without
workflow changes.

Assisted-by: Pi Coding Agent:Muse Spark 1.2

natsukium added 1 commit 2026-09-06 13:47:06 +09:00

nix: pin dev partition nixpkgs to root so dev and package share one revision ... 5b2e17be85

dev/flake.nix needs its own nixpkgs-dev for standalone lock, but when
evaluated via partitions.dev that second copy is never fetched by
consumers and would double-fetch for developers. Override
extraInputs.nixpkgs-dev with the root input so the dev partition
builds shells and checks against the shipped revision. Follows cannot
refer to the root flake directly, so this override is the partitions
workaround.

Assisted-by: Pi Coding Agent:Muse Spark 1.2

natsukium added 1 commit 2026-09-06 14:05:45 +09:00

nix: align dev pins with root so clippy and checks share one toolchain ... 473c7f7d3f

dev/flake.lock had drifted ahead of the root lock after the
partition split (rust-overlay c361 vs b916, nixpkgs-dev 17de0b vs
89570f), so nix develop resolved nightly 1.100 on the branch while
main still used 1.98. The newer nightly enables additional pedantic
lints that make cargo clippy fail under -D warnings.

Copy the root-equivalent pins into dev for the shared inputs so the
dev partition and standalone main share the same revisions. The
extraInputs override for nixpkgs-dev remains so the partition keeps
using a single store path even after the next Renovate update.

Assisted-by: Pi Coding Agent:Muse Spark 1.2

natsukium force-pushed nix/partition-dev-inputs from 473c7f7d3f to 0bf59f02fa 2026-09-06 14:46:27 +09:00 Compare

natsukium scheduled this pull request to auto merge when all checks succeed 2026-09-06 14:46:49 +09:00

natsukium force-pushed nix/partition-dev-inputs from 0bf59f02fa to 4dada3cf5c 2026-09-06 21:07:29 +09:00 Compare

natsukium merged commit 387a9e6855 into main 2026-09-06 21:20:04 +09:00

natsukium deleted branch nix/partition-dev-inputs 2026-09-06 21:20:04 +09:00

natsukium referenced this pull request from a commit 2026-09-06 21:20:04 +09:00

nix: isolate dev inputs in partitions.dev so consumers only fetch what they need (#162)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

No labels

priority/P0

priority/P1

priority/P2

release/v0.1.0

status/blocked

status/planned

type/bug

type/design

type/test-gap

type/tracker

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

natsukium/felis!162

No description provided.