WIP mosh dedicated package

[ymartin59]

sshfs/fuse now builds with meson/ninja
fuse requires udev to build

Updates

• fuse 3.8.0
• glib 2.62.2
• libevent 2.1.11-stable
• libffi 3.3
• socat 1.7.3.3
• sshfs 3.6.0
• tmux 3.0a

Motivation: tools updates
Linked issues: #3742, #4335

Checklist

• Build rule all-supported completed successfully
• Package upgrade completed successfully
• New installation of package completed successfully

[ymartin59]

@hgy59 fuse requires udev headers/library to build. I see two options:

• rebuild udev from source with same version as DSM
• create udev Conan package from DSM development kit (as a PoC of artifact creation/reuse)
  An opinion about it?

[hgy59]

@hgy59 fuse requires udev headers/library to build. I see two options:

* rebuild udev from source with same version as DSM

* create udev Conan package from DSM development kit (as a PoC of artifact creation/reuse)
  An opinion about it?

Hi @ymartin59
For udev I tried the same approach as in cross/he853. With definition of udevrulesdir the dependencies of udev are not required.

I succeeded to build with following meson parameters:
MESON_PARAMS = --prefix=$(STAGING_INSTALL_PREFIX) -Dexamples=false -Dudevrulesdir=$(STAGING_INSTALL_PREFIX)/lib/udev/rules.d -Duseroot=false

useroot=false is required for running the docker container with a non-root user (as I do).

With a different handling of the build folder I succeeded to build arch-x64.

But cross-compilation fails already in configure stage.
Didn't you create a cross-file yet?
IMHO it is required for cross-compilation and generation of cross-files should be added to the spksrc framework for meson build.

[hgy59]

@ymartin59 shall we really support meson builds?
It is very frustrating to work around all the not so obvious (= strange) behaviour of meson.
Just struggled about the need of a host compiler for cross compilation (mesonbuild/meson#5862)

[ymartin59]

@hgy59 Looks like you are already some steps ahead about it. No, I do not know meson enough to create cross-file. Let's try here as a PoC and then I will move support in framework.

[ymartin59]

Do not hesitate to use https://hub.github.com to get my PR branch and then push additional commits directly into it... I expect you are granted to do so.

[ymartin59]

Depends on #4203

[zyrill]

Since #4203 has been merged, maybe this PR is good to go as well? It still has the [WIP] flag though I think all of the todos are indeed done, are they not? Maybe that flag can be removed and this PR merged, @ymartin59

[hgy59]

Fuse is is still WIP #4335.
IMHO without fuse3 it makes no sense to create a new release of mosh.

[hgy59]

As mosh is already removed from synocli-net I have adjusted the title of this PR.

[ymartin59]

@hgy59 @th0ma7 May you please review this PR to determine if there is anything left to keep here. If you both agree with my opinion, just close this PR

[th0ma7]

@ymartin59 the fuse3 PR is not even close of being ready for a merge...

[th0ma7]

@ymartin59 I've added a link to [WIP] Update to libfuse3 #4335 just to keep track of things if we ever revisit.