From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Problems with update of sshfs
Date: Mon, 21 Dec 2020 18:06:29 +0100 [thread overview]
Message-ID: <99b3f273-1ea3-ee7c-02d8-2428dd91561c@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hallo All,
I saw that sshfs was in the core programme set and found that the version was at 2.2 and had been implemented in 2008.
sshfs is now at version 3.7.1 and thought I would update it. However I then found a problem.
From version 3.0.0 onwards (Jul 2017) sshfs build capability using Meson and Ninja was added. Installation was still able to be done via autotools as a fallback. From 3.3.0 (Sep 2017) autotools was dropped and the build can only be done via Meson and Ninja.
So the latest version that could still be built in IPFire using autotools is 3.2.0 (Aug 2017). It requires libfuse 3.1.0 or newer. libfuse 3.1.0 and 3.1.1 can still be built with autotools. From libfuse 3.2.0 autotools build support has been dropped.
Looking at sshfs, it is not clear to me what this is being used for in IPFire. The commit message in 2008 was "Added sshfs to supported fuse filesystems"
Any guidance or suggestions on what should be done with sshfs?
Regards,
Adolf
next reply other threads:[~2020-12-21 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 17:06 Adolf Belka [this message]
2020-12-22 12:20 ` Michael Tremer
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=99b3f273-1ea3-ee7c-02d8-2428dd91561c@gmail.com \
--to=ahb.ipfire@gmail.com \
--cc=development@lists.ipfire.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