On Wednesday 08 January 2014 15:37:30 Sami Kerola wrote: > On 8 January 2014 09:21, Karel Zak <kzak@xxxxxxxxxx> wrote: > > On Tue, Jan 07, 2014 at 01:44:07PM -0500, Mike Frysinger wrote: > >> On Tuesday 07 January 2014 05:19:35 Karel Zak wrote: > >> > On Tue, Jan 07, 2014 at 10:55:35AM +0100, Thomas Bächler wrote: > >> > > >> We already have such a cyclic dependency, since udevd depends on > >> > > >> libblkid+libuuid, and findmnt (from util-linux) depends on > >> > > >> libudev. > >> > > >> > >> > > > .. and nobody complains, good point :-) Thanks! > >> > > > > >> > > > Karel > >> > > > >> > > Actually, now that I know you care about these things, I am > >> > > complaining. > >> > > > >> > :-))) > >> > : > >> > > It has caused me (minor) trouble once already. > >> > > >> > It's possible (first time) to compile util-linux without libudev, > >> > compile systemd/udevd and then again recompile util-linux with > >> > libudev. > >> > > >> > IMHO libudev is very useful for findmnt and lsblk to get info about > >> > devices. > >> > > >> > Note that uuidd is absolutely unnecessary if you don't have huge SAP > >> > installation (-- it means unnecessary for 99% of the all Linux > >> > users). > >> > >> on a semi-related matter, it'd be nice if we could easily build > >> util-linux such that we only get the libraries. the plethora of > >> configure flags that control utils is a nightmare to manage, and i'm > >> not sure there's a flag for every utility (i haven't checked myself, so > >> i could easily be wrong). > > > > not yet ;-) > > > >> if that were in play, the circular loop would be easy to address -- > >> build util-linux once just for its libs, then udev/systemd, then > >> util-linux again. > > > > Yep, I know about the pain... I guess it would be enough to have > > something like > > > > ./configure --disable-all-builds --enable-libblkid > > > > where --enable/disable-all-builds controls the default of the > > enable_<name>= variables (the current default is usually "check") > > in configure. > > > > I'll try to implement it later (I'm working on new cfdisk now) -- or > > maybe some volunteer...? :-) > > I could try to fiddle around with autotools in next days/weeks. > > The one thing I am thinking to change immediately is > 's/--disable-all-builds/--enable-minimal/'. Unfortunately, due I'm just > a random contributor without distribution packaging experience at all I > will need few hints from real pros. Most important question being what > the minimal should include? I did think that option could be > --enable-libaries-only, but is that too minimal to be practical? i don't think general flags like "minimal" are useful. a knob that'd disable all binaries would though as then we could use the existing library knobs to select the exact ones we want to build/install. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
