From: "Claes Wallin" <gnu@clacke.user.lysator.liu.se>
To: Mark H Weaver <mhw@netris.org>
Cc: 21142@debbugs.gnu.org
Subject: bug#21142: Sshfs-fuse requires fuse
Date: Tue, 28 Jul 2015 21:27:13 +0200 [thread overview]
Message-ID: <CAGv_=BpzwvcqdLWjJLYhfi60dFHpz0xGKY_Ju86KnVZcNYeAEA@mail.gmail.com> (raw)
In-Reply-To: <87wpxk2wjh.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Jul 28, 2015 4:21 PM, "Mark H Weaver" <mhw@netris.org> wrote:
> Claes Wallin (韋嘉誠) <gnu@clacke.user.lysator.liu.se> writes:
> > On 27-Jul-2015 5:06 pm, "Andreas Enge" <andreas@enge.fr> wrote:
> >>
> >> Hello,
> >>
> >> when trying to execute sshfs from the sshfs-fuse package, I obtain
> >> fuse: failed to exec fusermount: No such file or directory
> >>
> >> I think that fuse should be a propagated input of sshfs-fuse.
> >
> > Maybe it's less intrusive toward the user to wrap sshfs to add fuse to
> > its PATH?
>
> Or patch the reference to 'fusermount' to be an absolute path?
That's even better!
> I haven't looked into this, so I don't know the feasibility of these
> approaches, but in general I think that 'propagated-inputs' should be
> avoided whenever there is a reasonable alternative.
>
> What do you think?
Yeah, installing a package should cause the minimum amount of surprise.
[-- Attachment #2: Type: text/html, Size: 1375 bytes --]
next prev parent reply other threads:[~2015-07-28 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:05 bug#21142: Sshfs-fuse requires fuse Andreas Enge
2015-07-27 17:23 ` Claes Wallin
2015-07-28 14:20 ` Mark H Weaver
2015-07-28 19:27 ` Claes Wallin [this message]
2015-11-29 11:18 ` Ludovic Courtès
2015-11-29 11:52 ` Claes Wallin
2015-11-29 14:58 ` Ludovic Courtès
2015-11-29 16:41 ` Claes Wallin
2015-11-29 17:01 ` Ludovic Courtès
2015-11-29 17:24 ` Claes Wallin
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='CAGv_=BpzwvcqdLWjJLYhfi60dFHpz0xGKY_Ju86KnVZcNYeAEA@mail.gmail.com' \
--to=gnu@clacke.user.lysator.liu.se \
--cc=21142@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.