On Thu, 2022-05-12 at 14:57 +0200, Lukáš Krejza wrote:
But i think, that dropping "upstream" version completely would be wrong.
I wasn't suggesting that. I rather thought of an alternatives-like approach.
4) The libfprint-tod and libfprint libraries are fully open-source, however, "tod" fork is basically useless without the closed source driver components. Main purpose of the fork is allowing loading external drivers as a libraries that are provided by vendors. This means that it is virtually useless without submitting the drivers (to packman or as a pullin packages)
Understood. Doing that in packman would be one option. The other is providing an installation script and/or simply a reasonable HOWTO or wiki page. Most of the time, users will just have to drop a given file to a certain location. This is similar to dropping a FW blob into /lib/firmware, which a lot of us have had to do before.
5) Actual question here: Does RPM support Provides: modalias and/or Supplements: modalias for USB IDs? I would use it for the closed driver
components, if possible.
A couple of packages use this feature, e.g. bluez-firmware. Regards, Martin