From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] util-linux: bump version to 2.28.1
Date: Thu, 11 Aug 2016 22:35:49 +0200 [thread overview]
Message-ID: <20160811223549.50c52467@free-electrons.com> (raw)
In-Reply-To: <1470938996-10477-1-git-send-email-rahul.bedarkar@imgtec.com>
Hello,
On Thu, 11 Aug 2016 23:39:56 +0530, Rahul Bedarkar wrote:
> +if BR2_PACKAGE_UTIL_LINUX_LIBUUID
> +
> +config BR2_PACKAGE_UTIL_LINUX_LIBUUID_FORCE_UUIDD
> + bool "force uuidd"
> + depends on !BR2_PACKAGE_UTIL_LINUX_UUIDD
> + help
> + Support uuidd even though the uuidd daemon is disabled.
What is the motivation for this new config option? Just that a new
--enable-<foo> has appeared in util-linux?
Also, I'm note quite sure to understand what it does, and therefore if
the chosen dependencies are correct. Could you give some more details?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-11 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 18:09 [Buildroot] [PATCH 1/1] util-linux: bump version to 2.28.1 Rahul Bedarkar
2016-08-11 20:35 ` Thomas Petazzoni [this message]
2016-08-12 13:35 ` Rahul Bedarkar
2016-08-19 21:45 ` Thomas Petazzoni
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=20160811223549.50c52467@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox