-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hyprland: adapt breaking changes #605
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Should have waited for a stable release with the commit before merging this. I forgot to mention that. |
Revert commit 762c07e ("hyprland: adapt breaking changes (danth#605)"), which falsely attempted to address a Hyprland breaking change [1] which is not yet available as a Hyprland release or Nixpkgs package, and therefore not available through Stylix's inputs.nixpkgs input. To address the future breaking change, update Stylix's inputs.nixpkgs input after the next Hyprland release is included in nixpkgs/nixos-unstable. [1]: hyprwm/Hyprland@d1638a0 Link: danth#608
Considering that it will take a while for the mentioned Hyprland commit to reach |
FWIW, there is a Hyprland release coming in a few days. |
…nge (#608) Revert commit 762c07e ("hyprland: adapt breaking changes (#605)"), which falsely attempted to address a Hyprland breaking change [1] which is not yet available as a Hyprland release or Nixpkgs package, and therefore not available through Stylix's inputs.nixpkgs input. To address the future breaking change, update Stylix's inputs.nixpkgs input after the next Hyprland release is included in nixpkgs/nixos-unstable. [1]: hyprwm/Hyprland@d1638a0 Link: #608
IIRC, Vaxry's Hyprland release schedule is not periodic, making it somewhat unreliable to wait on its next release. Either way, #608 has been merged. |
I know, he specifically said so in the Discord. I'm not making things up. |
since some people (admittedly probably not too many) do follow the latest master commits maybe it would be worth having a staging branch for stylix that can apply fixes like these before they would appear in nixpkgs? |
You can always use my branch, I'll make a take 2 draft PR so it's easier to find. #610 |
Mixing |
…nge (danth#608) Revert commit 762c07e ("hyprland: adapt breaking changes (danth#605)"), which falsely attempted to address a Hyprland breaking change [1] which is not yet available as a Hyprland release or Nixpkgs package, and therefore not available through Stylix's inputs.nixpkgs input. To address the future breaking change, update Stylix's inputs.nixpkgs input after the next Hyprland release is included in nixpkgs/nixos-unstable. [1]: hyprwm/Hyprland@d1638a0 Link: danth#608
…nge (danth#608) Revert commit 762c07e ("hyprland: adapt breaking changes (danth#605)"), which falsely attempted to address a Hyprland breaking change [1] which is not yet available as a Hyprland release or Nixpkgs package, and therefore not available through Stylix's inputs.nixpkgs input. To address the future breaking change, update Stylix's inputs.nixpkgs input after the next Hyprland release is included in nixpkgs/nixos-unstable. [1]: hyprwm/Hyprland@d1638a0 Link: danth#608
using workaround mentioned: danth/stylix#605
hyprwm/Hyprland@d1638a0