From: Philip Balister <philip@balister.org>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-devel@lists.openembedded.org,
jackie.huang@windriver.com
Subject: Re: [PATCH][meta-filesystems] fuse: Remove unneeded RDEPENDS on util-linux-mount
Date: Tue, 28 Feb 2017 09:37:58 -0500 [thread overview]
Message-ID: <474b3876-7b97-6303-cb88-a1b0175855c3@balister.org> (raw)
In-Reply-To: <1488108808-30079-1-git-send-email-mike.looijmans@topic.nl>
On 02/26/2017 06:33 AM, Mike Looijmans wrote:
> Fuse claimed to need util-linux-mount at runtime, which isn't true. This
> drags util-linux-mount into any image that uses fuse.
>
> Encountered no problems with busybox's mount command and fuse (and never
> had). Fuse doesn't call the "mount" program anywhere, so the dependency
> doesn't make sense anyway.
The RDEPEND was added by Jackie from Wind River in September 2015. Any
idea why it was needed then?
Philip
>
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
> ---
> meta-filesystems/recipes-support/fuse/fuse_2.9.4.bb | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/meta-filesystems/recipes-support/fuse/fuse_2.9.4.bb b/meta-filesystems/recipes-support/fuse/fuse_2.9.4.bb
> index 9a2dc11..153fcb4 100644
> --- a/meta-filesystems/recipes-support/fuse/fuse_2.9.4.bb
> +++ b/meta-filesystems/recipes-support/fuse/fuse_2.9.4.bb
> @@ -29,9 +29,6 @@ DEPENDS = "gettext-native"
>
> PACKAGES =+ "fuse-utils-dbg fuse-utils libulockmgr libulockmgr-dev libulockmgr-dbg"
>
> -# Fusermount requires features from the util-linux version of mount.
> -RDEPENDS_${PN}_class-target += "util-linux-mount"
> -
> RRECOMMENDS_${PN}_class-target = "kernel-module-fuse libulockmgr fuse-utils"
>
> FILES_${PN} += "${libdir}/libfuse.so.*"
>
prev parent reply other threads:[~2017-02-28 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 11:33 [PATCH][meta-filesystems] fuse: Remove unneeded RDEPENDS on util-linux-mount Mike Looijmans
2017-02-28 14:37 ` Philip Balister [this message]
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=474b3876-7b97-6303-cb88-a1b0175855c3@balister.org \
--to=philip@balister.org \
--cc=jackie.huang@windriver.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-devel@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 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.