Hardware database schema doesn't support linkage to devices nor packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Low
|
Unassigned |
Bug Description
The relaxng schema for the hardware database currently contains the following definition for a "target":
First, the term "target" is ambiguous and it would probably be preferable to express the term in Launchpad lingo. For example, linkage to packages which are already contained within Launchpad would be tremendously useful. So, an element named "packages" would probably be useful. In a similar way, linkage to devices should probably be use an element named "devices".
Second, the term "driver" is also ambiguous. Does this mean "kernel module"? Or, "something which drives the target"? Instead, it might be preferable to reference the "id" attributes which are already defined throughout the schema. For example:
Changed in launchpad-foundations: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: hwdb |
Right, the "software context" of a test needs indeed a better specification, but I think it is not sufficient to list packages only. A graphics card for example may be controlled by different Xorg drivers; a Postscript printer often understands PCL too, moreover, Gostscript provides more than one PCL driver; a scanner might be supported by more than one Sane backend.
I also agree that the term "driver" is not very precise. The main idea is that it is not enough to specify a package, but some component of a package, often called "driver", that is used for the test, because possible problems are often driver specific (or backend specific or thingy-specific or however else we might call it). Any suggestion for a better name than "driver"?
Hence we should specify both the package and the driver/ backend/ component/ ... of a package that is involved in a test.
While we can indeed reference most packages by their ID as listed in the <software> section of a submission, I am not sure, if this is possible in all cases. Some people for example install a printer or scanner driver provided by the device manufacturer as a tarball; others might install a package from the source code.
So I propose this schema change:
Examples for valid tags:
<driver package_id="2" name="ipw3945" /> name="samsung_ printer_ package" name="whatever" />
<driver package_