[Fingerforce-devel] Bug#840778: fprintd: Please announce supported hardware using AppStream

Laurent Bigonville bigon at bigon.be
Wed Nov 8 17:53:21 UTC 2017

On Fri, 14 Oct 2016 20:28:27 +0200 Petter Reinholdtsen <pere at hungry.com> 
 > Hi.


 > The fprintd package is one of the packages in the Debian archive that
 > should be proposed for installation when a given hardware dongle is
 > inserted or available. Thanks to the appstream system, this can now be
 > announced in a way other tools can use and act on. I've written the
 > isenkram system to ask the current user if hardware specific packages
 > should be installed when a new dongle is installed or already present on
 > a machine, and isenkram now uses appstream as one source for hardware to
 > package mappings.
 > You can read more about this on my blog,
 > <URL: 
 > Instructions on how to create the metadata XML file can be found in
 > <URL: https://wiki.debian.org/AppStream/Guidelines >.
 > It would be great if you could add an appstream metainfo file to the
 > fprintd package, with content similar to this:
 > <?xml version="1.0" encoding="UTF-8"?>
 > <component>
 > [...]
 > <provides>
 > <modalias>usb:v147Ep2020d*</modalias>
 > </provides>
 > </component>
 > If there are other hardware ids or kernel modules also supported by the
 > package, please add those too. :)

The problem here is that fprintd uses the libfprint library and it's 
that library which is implementing the real support of the fingerprint 

How are you seeing this then? Shouldn't the metadata file be added in 
the library instead?

More information about the Fingerforce-devel mailing list