Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - libinput-git

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: libinput-git 1.5.2.r71.g738a39f-1

Git Clone URL: https://aur-dev.archlinux.org/libinput-git.git (read-only)
Package Base: libinput-git
Description: A library to handle input devices in Wayland compositors
Upstream URL: http://freedesktop.org/wiki/Software/libinput/
Licenses: MIT
Conflicts: libinput
Provides: libinput=1.5.2.r71.g738a39f
Submitter: klusark
Maintainer: klusark
Last Packager: klusark
Votes: 7
Popularity: 0.625229
First Submitted: 2014-01-28 17:26
Last Updated: 2017-01-07 23:05

Required by (32)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Tharre commented on 2017-01-11 09:41

@klusark Sure, it's a dependency after all. The libwacom.h also exists under /usr/include/libwacom-1.0/libwacom/libwacom.h .

klusark commented on 2017-01-11 00:47

@Tharre do you have libwacom installed?

Tharre commented on 2017-01-09 20:32

Fails to build for me: http://pastebin.com/dVctC1VW

Seems like it needs some adjustments to the include path?

klusark commented on 2017-01-07 23:05

gim: Sorry, fixed now.

gim commented on 2017-01-07 10:33

It fails to build for me: http://slexy.org/view/s2HQtqrZsh

klusark commented on 2016-12-30 22:55

MrMeseeks: Why are you flagging this package out of date? "super buggy" isn't a good reason.

klusark commented on 2016-12-30 22:46

mickael9: Fixed. Thanks!

mickael9 commented on 2016-12-30 19:49

I think this is missing a libwacom dependency

klusark commented on 2015-04-22 17:15

thx1138: Look at pacman-git, it hasn't been updated since 2013, and it's maintained by an Arch developer.

thx1138 commented on 2015-04-17 22:41

> the version is set automatically on build.

Yes it is. Which means someone has to actually _build_ the package to discover what the current version is.

> What use case do you have that the version on the AUR matters?

Determining whether the git version is more recent, or significantly more recent, than the standard Arch version of the same package. Currently, the git version is not significantly more recent than the Arch version. But how would you know? This is why, for instance, the AUR search page prominently displays a "Version" column in the output. "libinput-git" prominently informs the person searching that the currently available version is "0.5.0..."

Which is wrong. Which is why it is rude to mis-manage information used by an automated search tool.

Also, tools like "yaourt" use the version information to determine whether a package update is available. "yaourt" will prominently inform the searcher that _no_ libinput-git update is available whenever the git version changes. Which is wrong. Which, again, is why it is rude, to mis-manage information used by an automated search tool.

You can "blame" the AUR search engine developer, or you can "blame" the yaourt developer for presenting these wrong results, but that would also be rude. These people have already been told implicitly to rely upon the version information provide by the package.