flake.nix: add xdph follows #8012
Merged
+6
−28
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
fixes a duplicate hyprland-protocols instance sometimes being created due to xdph not following hyprlands instance
|
IMHO it's better to update the flake right away. You can do |
|
@leiserfg I did, see flake.lock |
fufexan
approved these changes
Oct 7, 2024
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.
Describe your PR, what does it fix/add?
Fixes a duplicate
hyprland-protocolsinstance in flake.lock due to xdph not following hyprlands instance.Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
The removal of the second
hyprland-protocolsinstancehyprland-protocols_2in flake.lock could also be done in the next flake update.Is it ready for merging, or does it need work?
I'm currently using this in my own NixOS configuration, and from what I can see, everything is functioning as expected. Ready for merging :)