Package Details: libfprint-git 1:1.90.6.r3.g3560a0f-1

Git Clone URL: https://aur.archlinux.org/libfprint-git.git (read-only, click to copy)
Package Base: libfprint-git
Description: Library for fingerprint readers
Upstream URL: https://fprint.freedesktop.org/
Keywords: fprint
Licenses: LGPL
Groups: fprint
Conflicts: libfprint
Provides: libfprint, libfprint-2.so
Submitter: matthewbauer
Maintainer: timothy_gu
Last Packager: timothy_gu
Votes: 29
Popularity: 0.000000
First Submitted: 2009-09-01 02:39 (UTC)
Last Updated: 2020-12-16 21:14 (UTC)

Latest Comments

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

rindeal commented on 2018-09-25 23:07 (UTC)

I've developed a new driver for the proprietary binaries, which include support for VFS495 (among others). The source code and installation instructions are here - https://github.com/rindeal/libfprint-vfs_proprietary-driver.

SammysHP commented on 2018-08-14 09:41 (UTC)

@intelfx Yeah, this should be fine now, thanks! I'll delete/move my package libfprint-upstream-git.

intelfx commented on 2018-08-13 20:39 (UTC) (edited on 2018-08-13 20:39 (UTC) by intelfx)

@rocky7x I have since dropped the vfs495-daemon glue patch because it stopped applying and I have found no interest in forward-porting it again.

@SammysHP I believe now you have no concerns over this package?

rocky7x commented on 2018-08-13 13:55 (UTC)

Having VFS495 Validity device (138a:003f) and when I install this together with vfs495-daemon it doesn't work - throws No devices found - any idea? i added myself to plugdev and scanner groups...

nsood commented on 2018-06-06 15:53 (UTC) (edited on 2018-06-06 15:53 (UTC) by nsood)

For the time being, adding this line to prepare() in the PKGBUILD, before git apply, allows us to compile:

git checkout 3bf55a3e0766ca90f5befc1ed161b1c83005a962

Be warned though, this builds the last version of libfprint that did not migrate to Meson, and while it is relatively recent at the time of posting this comment, it might become outdated and unusable in time.

SammysHP commented on 2018-05-21 08:04 (UTC)

@intelfx

One and a half year later I want to ask you again if you can rename your package to something like "libfprint-validity-git" as it still contains a patch that is not and will not be included in upstream:

intelfx wrote:

Of course it won't be accepted by upstream at least due to license incompatibilities.

Meanwhile there are other packages which add custom patches, libfprint-vfs0090-git and libfprint-vfs0097-git.

charli9 commented on 2018-05-20 18:37 (UTC)

This package is broken since upstream changed to Meson instead of Autom4te

SammysHP commented on 2018-03-03 10:20 (UTC)

@thql

autom4te is included in the autoconf package which is included in the base-devel group. This group is a requirement for building packages from the AUR. Thus it is not necessary to include this dependency in the package.

thql commented on 2018-03-03 06:45 (UTC) (edited on 2018-03-03 06:47 (UTC) by thql)

There is a missing dependency in the package : autom4te

EDIT: or a typo, should it be automake instead?

intelfx commented on 2017-12-12 17:45 (UTC)

@oscar.h, @JUSHJUSH: look at the "Upstream URL" as indicated above. This is not a place to report bugs; I'm merely packaging libfprint.

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