[fprint] Planning libfprint API changes (2.x)

Bastien Nocera hadess at hadess.net
Wed Jul 10 12:21:02 UTC 2019


On Wed, 2019-07-10 at 14:09 +0200, Benjamin Berg wrote:
> Hi everyone,
> 
> so, I have worked on this for a while now, and I pushed my changes to
> the
>   
> https://gitlab.freedesktop.org/libfprint/libfprint/commits/wip/benzea/v2
> branch.
> 
> This is not yet quite complete. Some changes are more invasive,
> others
> are less so. Most drivers have been ported at this point (fixing a
> number of issues in the process).

Anything that could be backported? Failing that, an issue filed per
problem would go a long way towards cleanups for 1.0.

>  Unfortunately, I have only been able
> to test two of the drivers on real hardware.
> 
> It would be great if people could take a look and test this. For
> testing, you have two ways:
>  * Grab the git repository and build locally
>    - Run demo/gtk-libfprint-test as root from the build directory
>  * Grab the flatpak from the CI pipeline, then:
>    - Add e.g. the flathub repository (by going to flathub.org)
>    - flatpak install org.gnome.Platform/x86_64/3.32
>    - flatpak install --no-deps --bundle DOWNLOADED_FLATPAK
>    - Make sure your user can access the USB device in /dev/bus/usb
>    - flatpak run org.freedesktop.libfprint.Demo

The plan is to eventually have a portal to give access to the USB
device. This requires kernel functionality to be added which I'm
procrastinating on.

Cheers



More information about the fprint mailing list