Re: [OpenWrt-Devel] udev/libudev update
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 openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
Hi, On 02/11/2013 09:04 PM, Aleksander Morgado wrote: 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! Why do we need this at all? Most configurations out there do not use udev at all and use hotplug2 instead to keep the system small. 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? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
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! Why do we need this at all? Most configurations out there do not use udev at all and use hotplug2 instead to keep the system small. I know that hotplug2 is the preferred system to handle uevents, but given that udev is currently in the core packages in trunk, I'm assuming that not everyone uses hotplug2 and that there are users out there using udev and applications that rely on udev. So, why not update udev to latest upstream release? My use case, anyway, is to package ModemManager for OpenWRT; and as part of that I thought that updating udev (and including gudev in the process) would be a nice thing to have. Cheers! Would it be beneficial to just rewrite the core functionality of ModemManager to use hotplug2 and netifd? Yeah, rewriting ModemManager to use hotplug2, netifd, and why not ubus and libubox would be a nice project, but it would be a total rewrite :) Meanwhile, a small system with udev, glib/gio, dbus and ModemManager (with mmcli) is already a great win, if you are not very constrained by the hardware. -- Aleksander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
On 02/11/2013 09:04 PM, Aleksander Morgado wrote: 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? I'd actually like to enable libgudev compilation from the systemd/udev repo as well (in 'trunk'), which requires glib and gobject (in 'packages')... so same issue. -- Aleksander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
On 11-02-13 21:04, Aleksander Morgado wrote: Any suggestion? You forgot option #4: forget about the whole systemd madness, and migrate to eudev (1) Systemd bloat simply doesn't belong on an embedded system, IMHO. (1) http://www.gentoo.org/proj/en/eudev/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
On 02/11/2013 12:04 PM, Aleksander Morgado wrote: 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 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. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
You forgot option #4: forget about the whole systemd madness, and migrate to eudev (1) Systemd bloat simply doesn't belong on an embedded system, IMHO. (1) http://www.gentoo.org/proj/en/eudev/ That's not really a replacement; the developers of eudev themselves say that it's just a training project. http://www.h-online.com/open/news/item/Udev-fork-is-a-training-project-say-eudev-developers-1796664.html -- Aleksander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
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. -- Aleksander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
- Mail original - De: Aleksander Morgado aleksan...@lanedo.com À: OpenWrt Development List openwrt-devel@lists.openwrt.org Envoyé: Lundi 11 Février 2013 21:04:47 Objet: [OpenWrt-Devel] udev/libudev update 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! ... 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. LFS maintain a makefile to only build a minimal udev. http://www.linuxfromscratch.org/lfs/view/development/chapter06/udev.html Gilles ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] udev/libudev update
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. LFS maintain a makefile to only build a minimal udev. http://www.linuxfromscratch.org/lfs/view/development/chapter06/udev.html Ah! will give it a try tomorrow. Thanks. -- Aleksander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
