Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix darwin-rebuild PATH configuration

Open
#170 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
zsh
Domain
devops

Research direction

Review the PATH configurations in cfs.nix, personal.nix, and seneca.nix, then inspect the .zshrc changes around nix-daemon.sh. Verify that /run/current-system/sw/bin is retained in PATH and that darwin-rebuild is available after installation.

Written by the indexing model from the issue text.

Description

bug

Summary

Resolved issue where darwin-rebuild command was not found after installation due to PATH configuration problems.

Problem

  • /run/current-system/sw/bin was not in user's PATH
  • Nix-Darwin configurations were using lib.mkForce which prevented proper PATH merging
  • User's .zshrc was not able to control final PATH ordering

Solution

  1. Removed all lib.mkForce usage from PATH configurations in:

    • cfs.nix
    • personal.nix
    • seneca.nix
  2. Updated .zshrc to properly configure PATH after nix-daemon.sh:

    # Initialize path array from current PATH
    path=(${(s/:/)PATH})
    
    # Ensure darwin-rebuild is accessible
    if [[ -d /run/current-system/sw/bin ]]; then
        path=('/run/current-system/sw/bin' $path)
    fi
    

Key Learning

User shell configuration should have final control over PATH ordering. Nix should provide paths but not force ordering.

Related

  • This was discovered while working on MCP server module implementation
  • Solution documented in .claude/guides/lessons-learned-nix.md
Dominant language
Jupyter Notebook
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/dotfiles

All issues in aRustyDev/dotfiles

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.