Package Base Details: roccat-tools

Git Clone URL: https://aur.archlinux.org/roccat-tools.git (read-only)
Keywords: gui hardware keyboard mouse settings
Submitter: russo79
Maintainer: aaronfischer
Last Packager: aaronfischer
Votes: 55
Popularity: 0.102123
First Submitted: 2012-03-05 16:53
Last Updated: 2019-05-16 20:50

Pinned Comments

aaronfischer commented on 2019-03-28 20:13

@Gonzo2028: See here: https://www.reddit.com/r/linux_gaming/comments/5js1l2/im_stefan_achatz_stopping_programming_linux/

Stunts commented on 2017-01-05 13:13

@gonzo2028:
There are 2 alternative ways:
1. @aaronfischer splits the package into 25 different ones and whenever there is an update he will have to update 25 individual packages; good for the useres, not so good for the maintainer.
2. @aaronfischer "merges" all the files from the split packages into a single package. This will result in installing binaries, udev rules and .desktop files for 25 devices for every user. Less work for the maintainer, not practical for the users.

As is it, the maintainer maintains one single "split-package" and users that use an AUR helper such as yaourt, can uninstall the packages they don't need. This way users get to keep only the files they need to support their own device and the maintainer does not have to modify and commit 25 packages every time there is an update.

Hope this helps clear it.

aaronfischer commented on 2015-11-22 13:21

@edward_81: Please read the previous comments here. I've talked to Stefan about this. Every version of roccat-tools need a specific version of libgaminggear to work correctly. There are two options here: Consistent/reliable package and a little bit of hasle on upgrades -- or easy upgrade process and the chance of a broken package with weird bugs everywhere. I've choosen the first option.

edward_81 commented on 2015-10-03 15:31

Is possible to change the dependency line for libgaminggear from:
libgaminggear=0.11.1
to:
libgaminggear>=0.11.1
Because every time i try to upgrade the system with yaourt/aur, it complain that roccat-tool-common need that exactly version of libgaminggear.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

ryuzy commented on 2017-01-06 13:58

@Gonzo2028:
If you use an AUR helper like pacaur only the specified packages will be installed and not all of them.

mdemierre commented on 2017-01-05 15:52

@aaronfischer I think you forgot to include the new 90-uinput.rules in your latest commit (f2f8e2eef25ab4c880828b9fadf7b5829c5130d9). It still has the old checksum.

Stunts commented on 2017-01-05 13:13

@gonzo2028:
There are 2 alternative ways:
1. @aaronfischer splits the package into 25 different ones and whenever there is an update he will have to update 25 individual packages; good for the useres, not so good for the maintainer.
2. @aaronfischer "merges" all the files from the split packages into a single package. This will result in installing binaries, udev rules and .desktop files for 25 devices for every user. Less work for the maintainer, not practical for the users.

As is it, the maintainer maintains one single "split-package" and users that use an AUR helper such as yaourt, can uninstall the packages they don't need. This way users get to keep only the files they need to support their own device and the maintainer does not have to modify and commit 25 packages every time there is an update.

Hope this helps clear it.

Gonzo2028 commented on 2017-01-05 13:03

@aaronfischer: thanks, this fixed it.

Is there any way to avoid having all those keyboard-specific packages installed?
I assume i only need the roccat-tools-ryosmk and the roccat-tools-common.
Updating it means to rebuild all those packages -> this takes ages with yaourt.

Thanks in advance.

Stunts commented on 2017-01-05 10:30

@aaronfischer
Please look at the follow up regarding uhid here:
https://bbs.archlinux.org/viewtopic.php?id=221441

I let a small bug slip into the package. Sorry about that.

frederick_monk commented on 2017-01-05 06:57

@aaronfischer Thank you! That worked.

aaronfischer commented on 2017-01-04 21:49

@frederick_monk, @Gonzo2028: You need to reinstall the libgaminggear package. cmake changes the directory from cmake-3.6 to cmake-3.7. The definition files for libgaminggear still sit on cmake-3.6 and due to this fact, cmake can't find the it. So, reinstalling libgaminggear fixes the problem.

Gonzo2028 commented on 2017-01-04 11:35

It does not build for me:

CMake Error at CMakeLists.txt:84 (FIND_PACKAGE):
By not providing "FindGAMINGGEAR0.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"GAMINGGEAR0", but CMake did not find one.

Could not find a package configuration file provided by "GAMINGGEAR0"
(requested version 0.15.0) with any of the following names:

GAMINGGEAR0Config.cmake
gaminggear0-config.cmake

Add the installation prefix of "GAMINGGEAR0" to CMAKE_PREFIX_PATH or set
"GAMINGGEAR0_DIR" to a directory containing one of the above files. If
"GAMINGGEAR0" provides a separate development package or SDK, be sure it
has been installed.

frederick_monk commented on 2017-01-04 06:25

Hi,
following error occurs on 2 different machines(both x86_64):

CMake Error at CMakeLists.txt:84 (FIND_PACKAGE):
By not providing "FindGAMINGGEAR0.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"GAMINGGEAR0", but CMake did not find one.

Could not find a package configuration file provided by "GAMINGGEAR0"
(requested version 0.15.0) with any of the following names:

GAMINGGEAR0Config.cmake
gaminggear0-config.cmake

Add the installation prefix of "GAMINGGEAR0" to CMAKE_PREFIX_PATH or set
"GAMINGGEAR0_DIR" to a directory containing one of the above files. If
"GAMINGGEAR0" provides a separate development package or SDK, be sure it
has been installed.

aaronfischer commented on 2017-01-03 13:21

Thanks Francisco for your investigation and the PKGBUILD. I've made several changes on it so it will fit nicely into the package (and will remove after uninstalling the package). roccat-rools.install will take care of reloading the rules after update/install/remove.