[Paul Wise] > I would say that adding components/DEP-11 support to apt metadata is > a much better way to achieve this than copying parts out of the > Contents file. It is pretty close to equivalent anyway and is > cross-distro so it can be used by things like PackageKit. > > https://wiki.debian.org/DEP-11
[Petter Reinholdtsen 2014-03-06] > Absolutely. Then the needed information would be available > automatically for any apt user, and hw-detect in d-i can use it to > find firmware packages, even for non-official packages from > non-official apt sources. :) Now we know more about the state of DEP-11, and the implementation done by in Google Summer of Code project handle mime types, icons, etc, but not firmware and hardware information. So for Jessie, I believe we need to look at a different solution. > And the isenkram package would be able to use this too after > installation, if some firmware is needed to handle hotplugged > hardware. I've split the isenkram package in two yesterday, one isenkram-cli for the command line tools, and one isenkram for the GUI popup tool. Perhaps its isenkram-autoinstall-firmware script can be a starting point for handling firmware and hardware package installation from d-i? I plan to look into this before jessie, perhaps replacing the current discover support in the hw-detect package to make it happen. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
