@nsood : Patch updated, thanks!
I'm reluctant to add a provides=(libfprint) declaration to the PKGBUILD since this might result in ABI incompatibilities between the actual libfprint package and this one : as you've probably noticed, the git repository for libfprint-vfs_proprietary builds its own libfprint via a submodule. If this package provided libfprint, it would mean that it is binary-compatible with all applications that have been built against the real libfprint available in the repositories. Actually, a previous version of the PKGBUILD had a provides declaration.
Let me know what you think : I'm not heavily opposed to it, it's just that it might cause unnecessary trouble and weird segfaults for end users.
Pinned Comments
lighterowl commented on 2019-01-27 16:46 (UTC) (edited on 2019-01-27 16:46 (UTC) by lighterowl)
This package will not work with fprintd available in the standard repositories. Please build fprintd-vfs_proprietary, which provides the exact same functionality except one patch which disables some of systemd's stuff needed for the VFS daemon and external applications to interact.
For more information, please see https://github.com/rindeal/libfprint-vfs_proprietary-driver/issues/4#issuecomment-457719868 .