From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11811] lsblk (util-linux) should depend on libudev if available
Date: Fri, 03 May 2019 12:19:58 +0000 [thread overview]
Message-ID: <bug-11811-163-MuWGZSniCN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11811-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11811
--- Comment #5 from Carlos Santos <unixmania@gmail.com> ---
(In reply to Pete Morici from comment #3)
It would be possible to have a util-linux-libs package providing libblkid and a
util-linux package with the utilities, only. Another solution would be doing
the same as Fedora, on which libeudev is provided by a systemd-libs package on
which util-linux depends.
I will investigate both solutions and post the results as soon as possible.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-03 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 3:02 [Buildroot] [Bug 11811] New: lsblk (util-linux) should depend on libudev if available bugzilla at busybox.net
2019-04-30 7:00 ` [Buildroot] [Bug 11811] " bugzilla at busybox.net
2019-04-30 12:34 ` bugzilla at busybox.net
2019-04-30 12:56 ` bugzilla at busybox.net
2019-05-03 12:10 ` bugzilla at busybox.net
2019-05-03 12:19 ` bugzilla at busybox.net [this message]
2019-05-05 0:15 ` bugzilla at busybox.net
2019-05-05 2:15 ` bugzilla at busybox.net
2019-05-05 2:17 ` bugzilla at busybox.net
2019-05-05 2:21 ` bugzilla at busybox.net
2019-05-07 16:57 ` bugzilla at busybox.net
2019-05-09 17:19 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2020-11-04 21:57 ` bugzilla at busybox.net
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=bug-11811-163-MuWGZSniCN@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.