GNU bug report logs - #21142
Sshfs-fuse requires fuse

Previous Next

Full log

View this message in rfc822 format

From: Claes Wallin (韋嘉誠)
 <gnu <at> clacke.user.lysator.liu.se>
To: Mark H Weaver <mhw <at> netris.org>
Cc: Andreas Enge <andreas <at> enge.fr>, 21142 <at> debbugs.gnu.org
Subject: bug#21142: Sshfs-fuse requires fuse
Date: Tue, 28 Jul 2015 21:27:13 +0200

[Message part 1 (text/plain, inline)]

On Jul 28, 2015 4:21 PM, "Mark H Weaver" <mhw <at> netris.org> wrote:
> Claes Wallin (韋嘉誠) <gnu <at> clacke.user.lysator.liu.se> writes:
> > On 27-Jul-2015 5:06 pm, "Andreas Enge" <andreas <at> 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.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.