<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - add new pkg-config libudev-hwdb"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72562">72562</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>add new pkg-config libudev-hwdb
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>desrt@desrt.ca
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>The hwdb functionality of udev actually has very little to do with udev itself,
in the sense that it would be easily possible to have this in a very simple
standalone library.
Some people (colord) use the hwdb database as a hard dependency, but do not
require any of the rest of udev.
It would be nice if they could depend only on the hwdb component, so that other
platforms could implement the udev_hwdb API without having all of udev.
The attached patchset does some minor restructuring and introduces a new
libudev-hwdb.pc and libudev-hwdb.h which can be used as an entry to the
udev-hwdb functionality, without the need to use udev proper.
The changes are minimal -- we still only build one library, and the new .pc
file links this library. Having a separate .pc file and header, however, will
allow colord to depend only on the hwdb components.
It would also be possible to skip the last two patches in the series and have
colord declare a dependency on udev but only use udev_hwdb, but that would put
3rd party implementations in the awkward position of having to claim to be
'udev' while only implementing a small fraction of the API.
In fact, we could skip everything here entirely and have colord just start
passing NULL to udev_hwdb_new() but I would consider this to be excessively
evil.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>