From mboxrd@z Thu Jan 1 00:00:00 1970 From: Allin Cottrell Date: Wed, 12 Sep 2012 23:44:35 +0000 Subject: Re: udev fork Message-Id: List-Id: References: <20120912174951.GA32608@glow> In-Reply-To: <20120912174951.GA32608@glow> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, 12 Sep 2012, Bruce Dubbs wrote: > Greg KH wrote: >> On Wed, Sep 12, 2012 at 03:56:33PM -0500, Bruce Dubbs wrote: >>> Greg KH wrote: >>> >>>> What dependencies? Run time? Build time? And why are dependencies >>>> bad? Do you have no ram in your system for them? >>> >>> The configure scripts require packages that are not in LFS. >> >> Like what? Can't you add them? > > intltool, glib, gperf, gobject-introspection. > > intl needs XML::Parser. glib needs libffi and python and can use pcre, attr, > d-bus, gamin, and gtk-doc. gobject-introspection also needs glib and can use > cairo and gtk-doc. cairo needs libpng, glib, and pixman and can use > fontconfig, gtk+, xorg libraries (and on and on). Pkg X "can use" pkg Y (where Y is something that one might or might not want to install) is not an argument against requiring pkg X. I'm one who thinks (on the basis of experience with home-rolled systems), that systemd really is a smarter, faster, more comprehensible, and more user-manageable way to get a Linux system up and running than sysvinit plus a big mess of shell scripts. However, I take your point about some of the systemd dependencies, direct and indirect (even though systemd's configure script has a fair number of useful --disable-whatever options). Why intltool, for instance? Systemd has a --disable-nls option in its configure script. But this is in fact just automake fraud; there's really no way to disable nls (and everything it brings in, including intltool), so far as I can tell. -- Allin Cottrell Department of Economics Wake Forest University