From: Karel Zak <kzak@redhat.com>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: util-linux@vger.kernel.org, Sami Kerola <kerolasa@iki.fi>
Subject: Re: [PATCH] uuidd: use pkg-config to find systemd-deamon support
Date: Tue, 7 Jan 2014 11:19:35 +0100 [thread overview]
Message-ID: <20140107101935.GA2658@x2.net.home> (raw)
In-Reply-To: <52CBCF17.50706@archlinux.org>
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).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-01-07 10:19 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 [this message]
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
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=20140107101935.GA2658@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--cc=thomas@archlinux.org \
--cc=util-linux@vger.kernel.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