On 22 Jul 2013 18:19, "Michael Biebl" <<a href="mailto:mbiebl@gmail.com">mbiebl@gmail.com</a>> wrote: > > 2013/7/22 Kay Sievers <<a href="mailto:kay@vrfy.org">kay@vrfy.org</a>>: > > On Mon, Jul 22, 2013 at 3:32 PM, Umut Tezduyar <<a href="mailto:umut@tezduyar.com">umut@tezduyar.com</a>> wrote: > >> For an embedded system that is not using hwdb.bin, we are shipping > >> roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d. Is it > >> distributions responsibility to clean up .hwdb files after build or > >> should we have a configure option to exclude hwdb support? > > > > It's probably not really worth to compile-out the hwdb support, the > > involved code is quite small. > > > > Deleting/sub-packaging the ,hwdb source files (which are only needed > > to re-compile the database in /etc), or not compiling a the binary > > database at all should probably be a decision at the packaging/install > > level, and not a configure option. It should be reasonable easy to do > > step that at packaging/install time. > > > > Is the data in hwdb really optional, i.e. does it only contain strings > for representational purposes? In principle it can contain anything, so while it now mostly contain data for representation purposes, that's not really a safe assumption to make in general. For instance the keyboard database shipped with systemd contains quirks, and the database to be shipped with gphoto2 contains data to classify media devices (without which no cameras will be recognized as such by varies UIs). That said, there may be plenty of situations where you know you don't need a particular sub-database, so packaging these separately may make sense. Tom