Re: Problems with update of sshfs

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]

Hi,

I wouldn’t mind it sshfs is being dropped. I didn’t use it in quite a while.

But I suppose that we won’t get away with it much longer to not include ninja and meson. Many projects have moved away from autotools and started making packagers’ life hell.

I think Stefan might have built them for IPFire 2 before.

sshfs can be used to mount a remote file system on the firewall. It is handy for backups and for development and does not need anything else but the SSH daemon and SFTP on the remote side.

-Michael

> On 21 Dec 2020, at 18:06, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
> 
> 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
>