While I agree that 1130:0202 is a cut-n-paste error on my part, the intention was to fetch the relevant IDs from the udev rules. Among the many BTS reports I have sent to try to get machine readable hardware mappings into Debian, this one obvously included a mistake. Sorry about that.
I leave the decision on keeping or not keeping the hardware mapping in your capable hands. You know the package better than me. I just want to note that at least some of your argument seem to revolve around the idea that packages would be automatically installed based on the mapping provided. At least at the moment, this information is only used by those installing isenkram to get a list of possible packages to install. It is up to the user if they want to install it or not. Perhaps it will be more automatic in the future, perhaps also using other tools, but at least today it is not. As for the usefulness, I guess it both depend on the package and who evaluate it. I find it very useful to get information about packages useful for my current set of hardware automatically, so I do not have to sift through 50 000 packages to try to locate such packages manually. Thanks to the hardware mapping in Isenkram, I discovered a tool to get the battery status out of my wireless mouse the other day. I would not have discovered that this was possible without AppStream hardware mappings and isenkram. :) -- Happy hacking Petter Reinholdtsen
