all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se>
Cc: 21142@debbugs.gnu.org
Subject: bug#21142: Sshfs-fuse requires fuse
Date: Tue, 28 Jul 2015 10:20:50 -0400	[thread overview]
Message-ID: <87wpxk2wjh.fsf@netris.org> (raw)
In-Reply-To: <CAGv_=BoqmMSKHkSzm6-Rc01r1TqTXA2iX55kmz9Y0d6gwmC9EA@mail.gmail.com> ("Claes Wallin \=\?utf-8\?B\?KOmfi+WYieiqoCkiJ3M\=\?\= message of "Mon, 27 Jul 2015 19:23:20 +0200")

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?

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?

      Mark

  reply	other threads:[~2015-07-28 14:22 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 [this message]
2015-07-28 19:27     ` Claes Wallin
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=87wpxk2wjh.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=21142@debbugs.gnu.org \
    --cc=gnu@clacke.user.lysator.liu.se \
    /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.