>>> I'm trying to prepare an update of udev/libudev to latest upstream. As >>> you may already know, udev/libudev sources are now within systemd. I'm >>> not fully sure how to handle this issue; so I'm hoping to get some >>> advice here. Comments welcome! >>> >>> One option is to build systemd completely (e.g. without enabling any >>> special feature, just the bare minimum), and then package in the >>> udev/libudev packages only what we are interested for. This option would >>> require to have libcap and dbus as build dependencies; but these are not >> >> For what it's worth - and my requirements are often tangential to >> the OpenWrt developers ;-) I think this approach makes the most >> sense. There will almost certainly be someone sometime who wants >> the other bits, and building optional parts is best. I'd also >> like to see an update to udev, since there have been various >> bugs I've fought in older versions, so will take what I can >> get. >> > > I actually took that option here, slightly modified. I'm now building a > new 'systemd-udev' package in the packages repository instead of > updating the 'udev' one from trunk. I'll send tomorrow the patches for > comments to the mailing list. >
The following set of patches allow to compile a new 'systemd-udev' package in the [packages] repository using uClibc - didn't really try with other toolchains. Two of the patches will enable additional features in uClibc, which are needed for a proper compilation. The 'systemd-udev' package is created directly from systemd sources. Configure will disable all non-mandatory stuff, build the bare minimum (including systemd itself), but only package udev-specific files. Didn't enable libgudev yet; which is what I want to do next. Comments welcome, -- Aleksander _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
