On Wed, Jun 20, 2012 at 09:38:22AM +0200, Olav Vitters wrote: > On Tue, Jun 19, 2012 at 06:44:25PM +0200, Michael Olbrich wrote: > > This is not about the files from systemd. It's about the dependencies. > > Every user of a source based distro, that only wants systemd now has to > > first install dbus then udev, and then remove dbus again. > > Shouldn't the build system do this automatically?
Why should it? The equivalent for a normal distro would be to require e.g. perl in udev for a post-install script only. And then you expect the package manager to understand this and install perl before installing udev and remove it again afterwards. > I can understand it is inconvenient and makes things slower, but if > you're building from source anyway, a few build time dependencies > is ok? While I try to keep the dependencies at a minimum, this is not the real issue. I don't think you understand the embedded use-case. Right now what we have is basically a set of rules (how to build things) and some configuration (what to build). And with one command we get a root filesystem image. The configuration is more or less a list of packages to build. Now I need two lists, what to build and what to include in the final image. And while it is possible to implement this, it's also a lot more complex than fixing the real issue for udev. Regards, Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel