Dne středa 11. května 2022 20:18:35 CEST, Lukáš Krejza napsal(a):
Dne středa 11. května 2022 19:52:35 CEST, Andrei Borzenkov napsal(a):
On 11.05.2022 19:55, Lukáš Krejza wrote: ...
I cannot comment on possibility to replace libfprint with libfprint-tod in openSUSE, but as long as it works for other distributions may be it is an option ... someone needs to package it first :)
...
I think biggest problem problem with including will be closed source library for the libfprint-2-tod1-broadcom driver.
It is not part of libfprint-tod. The whole point of dynamic loading is to enable packaging drivers separately.
Providing your closed source driver for openSUSE is different matter entirely.
Yeah, exactly. I am adding Sp1rit to the loop.
@Sp1rit, do you plan to submit libfprint-tod to Factory? I noticed that there are some build failures for older Leap versions, but i don't know if these are required to be resolved before Factory submission.
For the driver, i have created libfprint-tod-broadcom in my home repo and will continue my work there, so i would be glad if anyone competent could comment if i should move it to Packman of create the package as a pullin, like for example Broadcom wireless firmware packages. Which one is preferred?
Thanks.
Gryffus
As a side note, Arch keeps both forks packaged and i think it is the correct path. From https://wiki.archlinux.org/title/fprint : "Some devices require a different fork of libfprint specifically made for touch-based sensors and not (yet?) merged with the main libfprint: libfprint- tod. This is available as libfprint-tod-git" We might ask fprint upstream if they plan to merge it or what is their opinion on the matter. Regards, Gryffus