Refactor Configurations with Per-machine Granularity Approach #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Resolve infinite evaluation by correctly deferring.
I can keep my preferred output layouts, but also enjoy the convenience of home-manager, darwin-rebuild and nixos-rebuild!
Read environment variables.
It needs rewrites.
My starship module is unnecessary...
Rather than "darwin-specified", they are my macbook-sepcified, in fact.
Since I've written a normalizing function, this patch is useless now. However, I do hope the flake system can support a more flexible paradigm in the future.
rennsax
added a commit
that referenced
this pull request
Oct 17, 2024
rennsax
force-pushed
the
refactor-per-machine
branch
from
5b248a2
to
5f0b0b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces significant changes by refactoring nearly the entire project.
After using Nix to manage my home configurations for some time, I found the Slot and Plugin paradigm I introduced in #4 is not as effective as I had hoped. The primary issue is that it’s unrealistic to expect different machines to share the same "slot" or several "plugins". Each machine's environment has subtle differences that are difficult to "de-couple".
To ensure full flexibility and extensibility, it's preferable to maintain a distinctive configuration for each machine, only sharing the modules and global variables.
Things Done:
home-manager,nixos-rebuildanddarwin-rebuildby utilizing a specific function. It allows me to use these scripts while applying the desired configuration layout.stdenv.hostPlatform.is{Darwin,Linux}.