This allows us to address the warning from the daemon.

Plugins should have calls to fu_device_set_vendor_id() to lock the device down
to one specific vendor. This vendor ID should match the ID set on the LVFS.

We should not use system quirks for version formatting or use the SMBIOS name
as a prefix for non-integral devices.

No functional changes.

It's not very common to have a system with a Synaptics MST hub or
a dock plugged in.  Avoid slowing down fwupd enumeration in the
common scenario.

As type-C docks become more common MST controllers in the host are
going to become rarer.  This should be a manageable whitelist
and prevent running the SMI on the majority of systems.

Enough places look for it that code duplication should go away.

This is certainly a problem lower in the stack, but at least provide
a method to block these systems from bringing down fwupd until it's
fixed.

For example if trying to run on a server, they might support some
dell SMI but are architected differently.

This was causing problems building on Jessie, and turns out to be unused
anyway:
   AttributeError: 'gi.repository.PangoCairo' object has no attribute 'font_map_get_default'
Signed-off-by: Philip Withnall <withnall@endlessm.com>

It's important to make sure that coldplug finished on thunderbolt
as this is what thunderbolt-power uses to make intelligent decisions

The only things that plugins can declare is that they should be run before,
after or never with regard to another plugin.

This allows people to build without docker without root.

Eventually fu-dell-common will not be used by synaptics, and it's
already not using this function.

Fixes https://github.com/hughsie/fwupd/issues/262

libsmbios is still used as a fallback in some cases, mostly
because it's not clear whether or not ProductSKU is available
in all instances.

testing should shield CI from migrations happening in unstable
can switch back to unstable as needed in future

The same thing can be done using BlacklistPlugins=test

The exact same thing can be done using BlacklistPlugins=udev

Some (HIDPPv1?) devices don't like being probed, and in some cases actually
stop working altogether.

Fixes bugs like #127 and #258

This allows a plugin to see if a GUID is supported in the AppStream metadata of
configured remotes. It allows plugins to skip devices that are not supported
and that do bad things when probed.

This reverts commit f194d685.

Fixes: https://github.com/hughsie/fwupd/issues/98

It's been superceded by the thunderbolt power plugin

Some (HIDPPv1?) devices don't like being probed, and in some cases actually
stop working altogether. As we only really support the K780, just whitelist
that and another test device.

Fixes bugs like #127 and #258