From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Problems with update of sshfs Date: Mon, 21 Dec 2020 18:06:29 +0100 Message-ID: <99b3f273-1ea3-ee7c-02d8-2428dd91561c@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2277083848278991868==" List-Id: --===============2277083848278991868== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 f= ound 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 f= allback. From 3.3.0 (Sep 2017) autotools was dropped and the build can only b= e 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 suppor= t 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 --===============2277083848278991868==--