On Mon, 2016-11-07 at 19:26 +0000, Mario Limonciello wrote: > That's a chicken and egg problem unfortunately. This type of information is > dependent upon the machine that fwupd is running on and can't be determined > at build time. I was mainly talking about the devices that can be found in this file: /lib/udev/rules.d/90-fwupd-devices.rules Those are a static set of devices not determined at runtime. I guess for those, prompting the user to install fwupd is a good idea. > If fwupd can be included by default in Debian I think a better experience can > be had though. For proprietary platforms that seems like a reasonable idea but for fairly open platforms like ARM/etc, I would much prefer all firmware to be packaged for Debian and flashed using flash-kernel or similar. > So for now I think it would be better for isenkram to do one of these: > 1) Query fwupd for updatable objects if it's installed. That sounds like a good idea, could you file a bug with the details? I am not aware how that should work. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part