Hey, 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 in the 'trunk' repo, but in 'packages' instead: * packages/utils/dbus * packages/libs/libcap These libraries are *not* needed for udev/libudev themselves, just to get other libs/bins from systemd built. If we ever want to package other stuff within systemd and/or systemd itself, this approach would be quite cleaner. A second option would be to completely forget about the dbus and libcap dependencies (e.g. patching configure,ac and autoreconf-iguring), and then make only the specific targets needed (e.g. "make libudev.la"). This approach is more complex and dirtier in the OpenWRT Makefile (e.g. lots of custom rules to install files), but at least doesn't build-depend on afterwards unneeded stuff. A third approach would be to actually provide a stripped down configure.ac and Makefile.am just with the udev/libudev stuff. Quite a nightmare to update these in each new udev/libudev release, though. By far, option #1 seems the cleanest and easiest to maintain. But I'm not sure how to handle the case of a package from 'trunk' requiring a package from 'packages'. Is that an issue at all? Any suggestion? -- Aleksander _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
