This repository was archived by the owner on Oct 28, 2025. It is now read-only.
lock flake-compat to root's input#5
Merged
zimbatm merged 1 commit intonix-community:masterfrom Jun 2, 2024
Merged
Conversation
Member
|
thanks! |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 isn't often relevant. But if you have inputs that themselves have a
flake-compatinput, you can end up using those by mistake. This locks the version used bydefault.nixto the input of the root node instead of which ever input happens to take theflake-compatname first.For example, I had my flake set up with #4, and eventually my
default.nixstopped working because one of my inputs got updated and itsflake-compatinput ended up taking theflake-compatname inflake.lock, while mine was underflake-compat_2.