nixos/base
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

remove nixpkgs overwrite #7

Merged
nonapode merged 1 commit from nonapode/remove-nixpkgs-overwrite into main 2025-11-26 18:47:32 +01:00
Conversation 3 Commits 1 Files changed 3 +18 -63
nonapode commented 2025-11-26 03:06:45 +01:00
Owner
Copy link

As we now have a pattern where every host as its own repository and forwards the actual nixpkgs version, remove the ability to overwrite the used nixpkgs but instead use the provided nixpkgs input (that can be injected by the normal flake inputs.follows approach).

As we now have a pattern where every host as its own repository and forwards the actual nixpkgs version, remove the ability to overwrite the used nixpkgs but instead use the provided `nixpkgs` input (that can be injected by the normal flake inputs.follows approach).
nonapode force-pushed nonapode/remove-nixpkgs-overwrite from 7ad8bb3192 to 74ac2c76d3 2025-11-26 10:30:12 +01:00 Compare
horscchtey approved these changes 2025-11-26 10:48:50 +01:00
horscchtey commented 2025-11-26 10:49:27 +01:00
Owner
Copy link

Please fix the resulting conflicts from pull request #5, otherwise this is good to go!

Please fix the resulting conflicts from pull request #5, otherwise this is good to go!
nonapode commented 2025-11-26 13:57:10 +01:00
Author
Owner
Copy link

Thinking about it again, I don't think we gain anything from this. While it probably will not be used (a lot/at all), it does not hinder us. We actually can remove all the inputs from the base flake itself, as the caller can inject the name to his liking and the base flake will be able to cope with it.

So I will simply remove the nixpkgs input (that was already intended to be overriden by the main-repo) and allow that main repo to specify what (main-repo-provided) input shall be used for the main nixpkgs of the system.

Thinking about it again, I don't think we gain anything from this. While it probably will not be used (a lot/at all), it does not hinder us. We actually can remove all the inputs from the `base` flake itself, as the caller can inject the name to his liking and the base flake will be able to cope with it. So I will simply remove the `nixpkgs` input (that was already intended to be overriden by the main-repo) and allow that main repo to specify what (main-repo-provided) input shall be used for the main nixpkgs of the system.
nonapode force-pushed nonapode/remove-nixpkgs-overwrite from 74ac2c76d3 to 72f2a2ddc0 2025-11-26 14:05:21 +01:00 Compare
nonapode deleted branch nonapode/remove-nixpkgs-overwrite 2025-11-26 18:47:33 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
horscchtey
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
horscchtey
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#8 apply nixfmt to tree of flakes
nixos/base
Reference
nixos/base!7
No description provided.