On Thu, 2011-06-02 at 18:06 -0700, Khem Raj wrote: > mdev or udev are image features so probably should be controlled by > IMAGE_FEATURES or some such
Well, yeah, but this is the thing with busybox: it is a monolithic executable, so you need to decide at configure time what features it's going to include. Although there is a separate busybox-mdev package, it just contains the auxiliary scripting and the bulk of the mdev code goes into busybox itself. This means that making mdev a pure IMAGE_FEATURE isn't practical, since it would basically require mdev to be always compiled in on the offchance that some image might want it. That would lead to code bloat for those images (probably the majority) which don't. Equally, having a single straightforward DISTRO_FEATURE to control mdev is not terribly satisfactory, since some distros might want to configure busybox with mdev enabled but actually use udev (or nothing) for some or all of their images. So, it seems that we really need both: a way for distros to configure whether busybox is built with mdev on or not, and then an IMAGE_FEATURE to control whether any given image gets mdev, or udev, or nothing. The former of those could be done as a DISTRO_FEATURE but, since it's only going to affect busybox, I'm not sure that there is much benefit in doing that; it seems like the distros could just as easily take care of that by direct manipulation of the busybox configuration. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
