Arch Linux User Repository

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

@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.

@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.

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.

also any specific reason to depend on specific version of libgaminggear? Why not use libgaminggear>=0.4.0 instead of libgaminggear=0.4.0 ? Updating to newer libgaminggear in your case requires either removal of roccat-tools or breaking deps.

You can subscribe to updates on sourceforge you know. And get email with each new release on the projects you follow. A very useful feature for a maintainer.

I've removed my comments because I found out the issue: my user was no longer in the group "roccat".

I just removed the old roccat-tools packages and installed the new ones. It's not like I use them all the time anyway.

How did you guys upgrade these packages? Installed fresh? Using --force doesn't seem to work with pacman -U and libgaminggear because it's not the package being installed that has depends issues it's the existing/already installed roccat-tools package. If it's changed to >= then one would be able to upgrade libgaminggear to 0.4.0 while still having previous roccat-tools installed, which would then allow roccat-tools to get updated at the same time and after the libgaminggear. I cannot do this for the current PKGBUILD cause I'm still stuck using the old packages. If you could graciously link us to the previous roccat-tools PKGBUILD? Then we'd be able to modify it from =0.3.0 to >=0.3.0 and then reinstall the old/existing package and then we'd be able to upgrade/install to this latest version and also do the same for that. = to >= otherwise this problem will arise next time the package(s) need updating. I not think this is any problem because you maintain both packages and the next time there is an update needing specific versions you control it. :] Thanks.

@Von, @pdq: The problem is that all roccat-tools NEED libgaminggear in version 0.4.0 and will not work with 0.3.0. So >= will fix the upgrade-problem, but is not correct :/ Is there no other solution sane for this problem?

I'm pretty sure roccat-tools is only needed for the configuration of roccat hardware. The kernel should have all the required drivers shipped with it since liek 3.0? Another option is to make package depend on >=version instead of ==version, so that the future versions of the dependency won't be prevented from being installed.