| Git Clone URL: | https://aur.archlinux.org/kwinft-git.git (read-only, click to copy) |
|---|---|
| Package Base: | kwinft-git |
| Description: | drop-in replacement for KWin with additional libwayland wrapping Qt/C++ library Wrapland |
| Upstream URL: | https://gitlab.com/kwinft/kwinft |
| Keywords: | kwinft |
| Licenses: | LGPL |
| Conflicts: | kwin, kwinft |
| Provides: | kwin, kwinft |
| Submitter: | haagch |
| Maintainer: | abelian424 |
| Last Packager: | abelian424 |
| Votes: | 11 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-04-15 23:41 (UTC) |
| Last Updated: | 2024-01-07 08:02 (UTC) |
Please, remove libkscreen-kwinft-git from deps, it no longer required
And advice from KWinFT maintainer:
But in general you could do it like that: make Disman a dependency of KDisplay and KDisplay a dependency of KWinFT. Then user only needs to install the KWinFT package.
Thanks for the info, it builds fine again now and doesn't require kscreenlocker-git anymore.
Tested by first installing wrapland-git kdisplay-git disman-git libkscreen-kwinft-git, and then building kwinft-git. I did not test the stable versions of those packages.
Headers issue was fixed by https://gitlab.com/kwinft/kwinft/-/merge_requests/22
libglvnd-git no longer required
Thanks for reminding me that I forgot to do this.
Turns out kwinft requires libglvnd-git because of this commit to compile https://github.com/NVIDIA/libglvnd/commit/4acb9be27db57413b18f25c6483b3451ba41d7e4#diff-d1377fbe747de154e1bfcf7221d3de67 but with libglvnd-git kwinft cmake doesn't find GL.
I'll look into it later.
Yes, I will update it soon, just got busy with work.
I don't know if you want to update the package to 5.19.0-beta, to make use of disman and kdisplay. I've uploaded both packages, but decided not to upload a kwinft as a few edits to the PKGBUILD will allow building to 5.19.0-beta. It seems kscreenlocker-git is still required, would be nice if that was updated as well even if it's simple enough to edit.
it would be nice to be able to use this package and kwin standard together in the sense of being able to select at startup to start plasma with this or plasma with the classic package ...
5.18.1 released https://gitlab.com/kwinft/kwinft/-/releases/kwinft%25405.18.1
Sorry to hear that. The surest way is probably to look in /var/log/pacman.log what *-git packages got installed and to install the normal versions of those.
Most of the plasma related -git packages are not actually required, just kscreenlocker-git. The kscreenlocker-git package is what pulls in all the plasma related -git packages and at this time it actually does not need them. When editing the kscreenlocker-git PKGBUILD and removing "-git" from all the dependencies, it will likely still work and build.
I hope that in the next few days some trusted user will package kwinft in the arch repos and there won't be a non git version needed in the aur.
How do you revert this, it failed to build and now my compositor is broken because half of everything is -git
These -git packages should not be providing the non git package names if they dont depend on them aswell, thats stupid
Pinned Comments
abelian424 commented on 2023-12-01 05:14 (UTC)
Until at least plasma-framework is updated to kf6 in the kde-unstable repo, this will not build. I don't know if it's possible to use KaOS repos, which are more bleeding edge than kde-unstable, but here is the link to mirrors if anyone wants to try: https://kaosx.us/packages/mirrors.php