From: Karel Zak <kzak@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "Thomas Bächler" <thomas@archlinux.org>,
util-linux@vger.kernel.org, "Sami Kerola" <kerolasa@iki.fi>
Subject: Re: [PATCH] uuidd: use pkg-config to find systemd-deamon support
Date: Wed, 8 Jan 2014 10:21:16 +0100 [thread overview]
Message-ID: <20140108092116.GA7516@x2.net.home> (raw)
In-Reply-To: <201401071344.09876.vapier@gentoo.org>
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...? :-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-01-08 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 23:39 [PATCH] uuidd: use pkg-config to find systemd-deamon support Sami Kerola
2014-01-07 8:58 ` Karel Zak
2014-01-07 9:38 ` Thomas Bächler
2014-01-07 9:54 ` Karel Zak
2014-01-07 9:55 ` Thomas Bächler
2014-01-07 10:19 ` Karel Zak
2014-01-07 18:44 ` Mike Frysinger
2014-01-07 18:51 ` Dave Reisner
2014-01-07 19:57 ` Mike Frysinger
2014-01-08 9:21 ` Karel Zak [this message]
2014-01-08 20:37 ` Sami Kerola
2014-01-08 20:44 ` Mike Frysinger
2014-01-08 22:28 ` Sami Kerola
2014-01-09 8:54 ` Karel Zak
2014-01-09 16:56 ` Mike Frysinger
2014-01-10 14:29 ` Sami Kerola
2014-01-07 11:20 ` Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140108092116.GA7516@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--cc=thomas@archlinux.org \
--cc=util-linux@vger.kernel.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox