[Debian-lego-team] Bug#877297: Bug#877297: libnxt: usb:v03EBp* too inclusive, leads to false positive matches

[Petter Reinholdtsen]

[Nicolas Schodet]
> I think so, could you check you have the same product id on your NXT?

I guess, but am not quite sure how to check.  Do you have a recipe?

>> Alternative, perhaps that USB ID should not be listed in the appstream
>> metainfo file?  I suspect I got the ID from one of the udev entries in
>> one of the other lego related packages:
>
> What are the consequences when several packages use the same
> identifier?

The appstream information is used to present package information to
those that are looking for what to install, typically in graphical
software helpers.  The only user of the hardware information that I am
aware of, is the isenkram system I wrote, which will trigger every time
it see some new hardware inserted into the machine, look up packages
claiming support for this hardware and pop up a prompt suggesting to
install these packages.  It can also look up already present hardware
and identify firmware packages requested by the kernel.

So if several packages use the same identifier, several packages will be
proposed to the user.

> I do not think there will be many SAM-BA in the wild, unless you are
> working with a SAM91 dev board. What would be the consequence for
> someone working with such a board?

The consequence is that isenkram will propose to install lego related
packages for this bord, which will confuse the user and not really help
them in any way.

-- 
Happy hacking
Petter Reinholdtsen