Skip to content
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

[Issue] why hyprland-git/ swaylock? #158

Closed
clsty opened this issue Dec 29, 2023 · 2 comments
Closed

[Issue] why hyprland-git/ swaylock? #158

clsty opened this issue Dec 29, 2023 · 2 comments

Comments

@clsty
Copy link
Collaborator

clsty commented Dec 29, 2023

  • I have read the instructions and I have a problem with branch: Illogical_impulse

The issue

I'm wondering that is it necessary to use hyprland-git in AUR? Because Arch Linux has already a package named hyprland.
After all, hyprland-git is less stable.

Another thing is that

swaylock and swaylock-effects-git are in conflict. Remove swaylock-effects-git? [y/N]

I mean, you can't install swaylock and swaylock-effects-git together in a script.

@clsty clsty changed the title [Issue] why hyprland-git [Issue] why hyprland-git/ swaylock? Dec 29, 2023
@clsty
Copy link
Collaborator Author

clsty commented Dec 29, 2023

I'll try to make a PR, if you don't mind.

end-4 added a commit that referenced this issue Dec 30, 2023
@end-4
Copy link
Owner

end-4 commented Dec 30, 2023

  • about swaylock, oops
  • about hyprland, i listed hyprland-git but actually i just compile the latest version manually
    • by using the development version i get exciting new features that are announced in its discord server once in a while
    • i sometimes make contributions so i just got used to staying up to date
    • you can use normal hyprland if it works. but if there's a breaking change on -git i normally try to update as soon as i can. if you just grab my dotfiles once and don't update it then it likely doesn't matter

@clsty clsty closed this as completed Dec 30, 2023
end-4 added a commit that referenced this issue Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants