From: Saul Wold <sgw@linux.intel.com>
To: jackie.huang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] udev: add runtime dependency on blkid
Date: Mon, 08 Jul 2013 12:35:43 -0700 [thread overview]
Message-ID: <51DB148F.9020702@linux.intel.com> (raw)
In-Reply-To: <f3947aac42370ea5f114852fd677ff1689a9b7ca.1373267292.git.jackie.huang@windriver.com>
On 07/08/2013 12:10 AM, jackie.huang@windriver.com wrote:
> From: Jackie Huang <jackie.huang@windriver.com>
>
> udev requires blkid, but this wasn't explicit. Note that the
> dependency is on util-linux specifically, the one from e2fsprogs
> won't work.
>
Doesn't udev use an internal builtin-blkid? Or is the configure finding
that we have util-linux and using it instead of the built-in?
If it's a configure test, then it might need to be a DEPENDS, not RDEPENDS.
Sau!
> Signed-off-by: Andy Ross <andy.ross@windriver.com>
> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> ---
> meta/recipes-core/udev/udev_182.bb | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/udev/udev_182.bb b/meta/recipes-core/udev/udev_182.bb
> index d66292e..114a557 100644
> --- a/meta/recipes-core/udev/udev_182.bb
> +++ b/meta/recipes-core/udev/udev_182.bb
> @@ -5,5 +5,9 @@ PR = "r7"
> # module-init-tools from kmod_git will provide libkmod runtime
> DEPENDS += "module-init-tools"
>
> +# Needs blkid from this particular package. The one in e2fsprogs is
> +# old and incompatible.
> +RDEPENDS_${PN} += "util-linux-blkid"
> +
> SRC_URI[md5sum] = "1b964456177fbf48023dfee7db3a708d"
> SRC_URI[sha256sum] = "7857ed19fafd8f3ca8de410194e8c7336e9eb8a20626ea8a4ba6449b017faba4"
>
next prev parent reply other threads:[~2013-07-08 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 7:10 [PATCH 0/1] udev: add runtime dependency on blkid jackie.huang
2013-07-08 7:10 ` [PATCH 1/1] " jackie.huang
2013-07-08 19:35 ` Saul Wold [this message]
2013-07-08 19:47 ` Andy Ross
2013-07-09 2:06 ` jhuang0
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=51DB148F.9020702@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.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