| Git Clone URL: | https://aur.archlinux.org/hyprland-git.git (read-only, click to copy) |
|---|---|
| Package Base: | hyprland-git |
| Description: | Hyprland is an independent, highly customizable, dynamic tiling Wayland compositor that doesn't sacrifice on its looks. |
| Upstream URL: | https://github.com/hyprwm/Hyprland |
| Licenses: | BSD-3-Clause |
| Conflicts: | hyprland |
| Provides: | hyprland |
| Submitter: | hertog |
| Maintainer: | Vaxry (zjeffer, alba4k) |
| Last Packager: | alba4k |
| Votes: | 94 |
| Popularity: | 8.30 |
| First Submitted: | 2022-04-12 20:26 (UTC) |
| Last Updated: | 2024-10-17 15:07 (UTC) |
@h3ss
This is very strange. I'm using yay & it's not seeing an update & have not seen one since I installed the hyprland-git. Just to check I installed paru, but there is no difference. I guess I'll need to figure this one out.. (or maybe I'll just switch to the regular upstream version, since the bug I needed a fix for is now fixed there too)
@sinasina Packaged affixed with -git should automatically track the corresponding git repository. The pinned comment from @memchr was because people were marking the package as outdated due to the version number not being updated on this webpage. It does not need to be updated here because it tracks the source git repo.
If your AUR helper is not seeing the updates, that would be a problem with the AUR helper, not this package. I can tell you that my machines see updates to this package multiple times every day, immediately after the git repo is updated, so it is working correctly for me. (I'm using paru for my AUR helper)
Does the pinned comment mean that AUR helpers will not see the updates, thus we should just reinstall if we want to get the latest git patches?
@glamprou26 See the pinned comment, this is a git package.
Latest Git commit fixed this: Whenever a window or layersurface is closed, there's a high chance vram consumption will go up by 10mb and such memory won't be freed, eventually consuming all vram and making the system unusable. Please update the package!
Sorry, I should have mentioned it here: I already submitted an issue to hyprlands github. The fix has been merged two hours ago (https://github.com/hyprwm/Hyprland/pull/3950) and the package successfully builds again.
Oh yes, my bad. I never looked at the PKGBUILD of this package. I am really sorry for wrong suggestions. I will try to get it fixed in the UPSTREAM
@akshettrj
Thank you for your work. However, I suggest you report this issue upstream, as the patch file subprojects/packagefiles/wlroots-meson-build.patch needs to be fixed.
The package fails to build because the Hyprland upstream has changed the wlroots sover from 12032 to 13032 in this commit: https://github.com/hyprwm/Hyprland/commit/af5d06593f83344e20537ad5ec7a780eda4fce87
suggested changes: https://aur.archlinux.org/packages/hyprland-nvidia-git#comment-945045
Is this package compatible with NVIDIA GPUs? I see that AUR has hyprland-nvidia and hyprland-nvidia-git packages but someone told me that hyprland and hyprland-git packages should work with NVIDIA GPUs. Is it correct? If so, what is the difference between hyprland{-git} package and hyprland-nvidia{-git} package?
Pinned Comments
zjeffer commented on 2024-07-17 16:50 (UTC) (edited on 2024-07-17 16:52 (UTC) by zjeffer)
Tips & tricks, common issues
using ccache/sccache
Precompiled headers (PCH) was enabled by default, this would most likely invalidate the compiler cache if any of the upstream header files change. To disable PCH, add the meson build option
-Db_pch=falsetobuild().Build with specific pull requests
Use
pick_mr <pull request number>at the end ofprepare()to merge pull requests locally. For example, to merge https://github.com/hyprwm/Hyprland/pull/6268, useEnable legacy renderer
In the
build()function, add-D legacy_renderer=trueto meson setupCompilation errors
If you encounter compilation errors, try the following first:
protocols/, such asprotocols/linux-dmabuf-v1.hpp, then rebuild or installhyprwayland-scanner-git;makepkg --cleanbuild.Symbol not declared
Errors like
<symbol> was not declared in this scope<symbol> has not been declaredare usually caused by missing headers. Please consider reporting this upstream or creating a pull request if it has not already been done.