Search Criteria
Package Details: libinput-gestures 2.78-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/libinput-gestures.git (read-only, click to copy) |
---|---|
Package Base: | libinput-gestures |
Description: | Actions gestures on your touchpad using libinput |
Upstream URL: | https://github.com/bulletmark/libinput-gestures |
Keywords: | gestures libinput multitouch touchpad |
Licenses: | GPL-3.0-or-later |
Conflicts: | libinput-gestures-git |
Submitter: | bulletmark |
Maintainer: | bulletmark |
Last Packager: | bulletmark |
Votes: | 96 |
Popularity: | 0.062968 |
First Submitted: | 2016-08-14 04:06 (UTC) |
Last Updated: | 2024-11-21 07:29 (UTC) |
Dependencies (5)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libinput (libinput-noaccumAUR, libinput-multiplierAUR, libinput-three-finger-dragAUR)
- python (python37AUR, python311AUR, python310AUR)
- wmctrl (optional) – required for _internal command, as per default configuration
- xdotool (xdotool-gitAUR) (optional) – simulates keyboard and mouse actions for Xorg or XWayland based apps
Latest Comments
« First ‹ Previous 1 2 3 4 Next › Last »
bulletmark commented on 2023-10-18 22:35 (UTC)
@yochananmarqos, of course I realize that there is no "need" to add the
conflicts
. However, as the maintainer oflibinput-gestures
I know it can not co-exist with that other package so what is wrong with specifying thatconflicts
explicitly? I consider it "documentation" within the PKGBUILD about that other package. I can't see any harm adding that explicitly and I don't see anything in the Arch docs prohibiting or recommending against it.yochananmarqos commented on 2023-10-18 14:21 (UTC)
@bulletmark:
libinput-gestures-git
provides and conflicts withlibinput-gestures
. There's no need to add any conflicts here as packages already provide and conflict with themselves.xiota commented on 2023-10-18 01:41 (UTC)
https://wiki.archlinux.org/title/PKGBUILD
bulletmark commented on 2023-10-18 01:15 (UTC)
@xiota, this package conflicts with
libinput-gestures-git
so why should I removed thatconflicts
?bulletmark commented on 2023-10-18 01:13 (UTC)
@xiota, if you wanted a response or action then you should have provided a justification + link to give your comment some authority. I saw that post a month ago and just assumed it was random odd unsolicited spammy brain-fart like we often see around here and so ignored it.
xiota commented on 2023-10-18 01:00 (UTC) (edited on 2023-10-18 01:05 (UTC) by xiota)
Flagged because you did not respond at all to previous comment for a month.
AUR Submission guidelines:
The rename exception does not apply here.
Also, the
conflicts
should be removed becauselibinput-gestures-git
alreadyprovides
/conflicts
with this package.bulletmark commented on 2023-10-18 00:22 (UTC)
@xiota, please provide a reference for your demand. Also, please don't flag a package out of date unless it is actually out of date.
xiota commented on 2023-09-20 13:31 (UTC) (edited on 2023-10-18 00:03 (UTC) by xiota)
Please remove
replaces
directive to comply with AUR submission guideline.labaman commented on 2022-08-14 14:37 (UTC) (edited on 2022-08-14 14:37 (UTC) by labaman)
@bulletmark, yes, I wouldn't install these two packages together either - no need, but when I decided to try Garuda Linux - that package was part of the input device support meta-package, and installing the usual X11-Gestures+touchegg bundle - I got the described lags when processing gestures. Considering that I have quite a high-performance PC, it's probably not in the load that this software produces on the CPU, but in the fact that these 2 programs simply interfere with each other, trying to process the same events in their own way. Also thanks for the tip - I will definitely describe the issue on the developer's github.
bulletmark commented on 2022-08-12 00:40 (UTC)
@labaman, I don't see why anybody would ever choose to run
libinput-gestures
in parallel with touchegg but if they really want to then I don't see they should not be allowed to.libinput-gestures
should use tiny CPU etc if you have configured it correctly (apart from whatever the scripts/programs you configure for actions use). It is also standalone and should certainly not conflict in any system sense with any other program. Raise an issue if you think it does.« First ‹ Previous 1 2 3 4 Next › Last »