On Sun, Feb 18, 2018 at 8:49 PM, Bastian Blank wrote:
> Well, if you need something, in this case some udev rules to actually
> be able to access the hardware, then you should recommend it. And as
> chromium does not pull in the library, then somehow it needs to get the
> udev rules.
Alternately, you plugin the hardware and your desktop software installer notices and prompts you to install the required packages. If the relevant packages have the relevant metadata this can work:
https://lists.debian.org/debian-devel-announce/2016/11/msg00008.htmlAnnouncing supported hardware via AppStream
-------------------------------------------
If you are maintaining a package that supports a specific set of
hardware, it would be great if you could add[15] some metadata about
which hardware is supported. By doing so, you will enable users to
discover your package when they plug in a new device supported by your
package. Users can use the isenkram[16] package to discover packages
related to their hardware. If your package contains udev rules, it
probably needs some AppStream metadata.
-- Paul Wise & Petter Reinholdtsen
[15] https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware
[16] http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
--
bye,
pabs
https://wiki.debian.org/PaulWise