Age | Commit message (Collapse) | Author |
|
NO VERSION BUMP, only pkgrel.
A number of changes was made not in either branch to make
wootility-appimage continue using “wootility” and also just some general
clean-ups. E.g., -lekker package doesn’t have anything systemd, so no
need for references to unit files nor xboxdrv and current udev rules do
not require the user to be in the “input” group.
See also commit 053e52e7f354c7a4ebdd1b225a3753d986d722c9
|
|
|
|
As per current version of
https://help.wooting.io/en/article/wootility-configuring-device-access-for-wootility-under-linux-udev-rules-r6lb2o/
|
|
Incl. updated udev rules from
https://help.wooting.io/en/article/wootility-configuring-device-access-for-wootility-under-linux-udev-rules-r6lb2o/
|
|
Reflects latest version of
https://wooting.helpscoutdocs.com/article/34-linux-udev-rules as of
this commit.
|
|
As per https://wooting.helpscoutdocs.com/article/34-linux-udev-rules
|
|
Instead of MODE and non-existing GROUP.
See:
- https://wiki.archlinux.org/index.php/Users_and_groups#Pre-systemd_groups
- https://wiki.archlinux.org/index.php?title=Talk:Udev&oldid=437293#Use_of_.27uaccess.27_instead_of_GROUP_and_MODE.3F
|
|
The rules are for the Wooting keyboard(s), not specifically for
Wootility (though they may be needed for Wootility to work).
|