fix(asahi): set hardware.asahi.enable explicitly

Upstream will stop defaulting hardware.asahi.enable to true and currently emits an evaluation warning to that effect. Set it explicitly on the lyrathorpe-mbp (MBP-Asahi) host to silence the warning and be robust to the future default change. Verified the warning no longer appears in the host toplevel eval.
2026-07-14 16:07:48 +01:00
1 changed files with 0 additions and 11 deletions
@@ -51,17 +51,6 @@
  home.shellAliases = {
    docker = "/run/current-system/sw/bin/docker";
  };
  # Source the (nix-unmanaged) Jenkins credentials file into every zsh, so the
  # JENKINS_UCE_/JENKINS_STF_ tokens are exported for all shells and anything they
  # launch -- the Jenkins MCP servers read them via ${JENKINS_*} expansion.
  # envExtra lands in ~/.zshenv, which zsh sources for login, interactive, and
  # non-interactive shells alike. Guarded so a missing file never breaks a shell;
  # the file holds secrets, so it is kept out of the world-readable nix store.
  programs.zsh.envExtra = ''
    [ -f "$HOME/.jenkinsenv" ] && . "$HOME/.jenkinsenv"
    [ -f "$HOME/.splunkenv" ] && . "$HOME/.splunkenv"
  '';
  programs.tmux = {
    # kube context/namespace in the status line. kube-tmux is pinned as a flake
    # input (it is not in nixpkgs), so the script is always present in the store.