Comment 17 for bug 1305839

Some responses to Dave's comments:

* Yes, it was done quickly and isn't perfect. It's a minimum useful set of functionality to address a real use case and that improvements can be added iteratively with the benefit of getting feedback from users in the meanwhile.

* fastpath can be added without a lot of extra work; we're not doing anything that prevents it from being added, I'd just rather get one install path working reasonably well before trying to get two working.

* The yaml file can be edited by an admin to add additional drivers. Yes, some sort of simplestreams like approach will probably be used to replace or augment the yaml file in the future, and yes, there will be some complication in the upgrade to whatever the new source is as we'll have to maintain user additions/edits. I don't see that as insurmountable though.

* I've posted a branch now that inserts the key directly into the yaml instead of retrieving it via http. Still working on a way to securely retrieve the udeb. The repo has a sha1 on the udeb; just need to work out how to validate the repo's sha1 now.

* There's always a possibility for multiple drivers to be required. We've done nothing that precludes adding that capability in the future, but it isn't a supported use case for today (and I haven't seen any real use cases that require it yet).

* Other arches could require it - adding support for other arches shouldn't be very difficult, but wasn't required to be useful here and is something that can added iteratively.

* HWE Kernel FFe bug 1281765: I don't know what the plans are here.