Package Details: g13-git 20160120-5

Git Clone URL: https://aur.archlinux.org/g13.git (read-only)
Package Base: g13
Description: Userspace driver for the Logitech G13 Keyboard
Upstream URL: https://github.com/ecraven/g13
Licenses: unknown
Submitter: punkrockguy318
Maintainer: khampf
Last Packager: khampf
Votes: 5
Popularity: 0.011433
First Submitted: 2015-09-04 03:37
Last Updated: 2016-04-03 17:18

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

khampf commented on 2017-06-06 13:01

It breaks every time libboost gets updated, a recompilation is needed to make it operational again. Not sure on how to solve this as pinning libboost version would make me notice earlier but a recompilation with theese sources as is do work on all versions of libboost.

punkrockguy318 commented on 2017-06-05 23:29

@Skylead
Are you still having this issue? I just recompiled today and didn't have any shared library issues

Skylead commented on 2017-06-02 22:10

Broken with boost 1.64.0

g13d: error while loading shared libraries: libboost_program_options.so.1.63.0: cannot open shared object file: No such file or directory

khampf commented on 2016-06-07 20:29

osvein: I have given it thought but not done anything about it, has to do with original PKGBUILD submitted before I maintained it. I will take a closer look soon

osvein commented on 2016-06-03 16:42

You probably don't want pkgbase to be something else than pkgname, unless it's a split package, which it currently isn't. If you just want a variable in the PKGBUILD which does not include the -git suffix, a better approach is to create a seperate variable, eg. _pkgname.

What you probably do want, however, is to declare the package a provider of g13.

khampf commented on 2016-04-03 16:23

jukebone: You're right, we should be using -r. I just set it up that way when testing initially and the number 613 reminds me of g13

jukebone commented on 2016-04-03 07:10

Why do you create the group and user with the fixed GID/UID of 613? This might clash with existing accounts, which it did for me. Maybe you should try -r for groupadd and useradd instead of hardcoding the IDs.

brittyazel commented on 2016-02-29 21:58

Awesome thanks. I'm just excited to finally have my g13 working in a way that is practical, and I'm just trying to do my part to help out. Let me know if you need me to test any changes.

khampf commented on 2016-02-29 19:21

I also got the "remove primary group of user" error but have sinced changed the order in which group and user g13 are deleted. The service should of course be stopped first, I will add that to the uninstall part next time around.

Why I left those parts commented out is due to the possibility of errors in the udev-rules, they are not well tested yet. They might be considered a bit more safe now but I think other packages might have problems with /dev/uinput too and this way of fixing it might clash with others. And it's a hack at best, using "uaccess" by itself should work but it does not.

Your wiki edits were fine so I let them be, uinput is mentioned a lot now but I will edit the wiki again when I'm certain uinput permissions are working.

brittyazel commented on 2016-02-27 18:48

I made some minor wiki changes for clarifications sake, please edit them as you see fit