One aspect that I didn't check fully, but that worries me a bit is how can preserve fuse and fuse3 to be installed together (as some out-archive components such as virtual machine additions or other pre-compiled binaries may still depend on libfuse and fusermount).
Now, this is not a problem for the library, but it is for the fuse/fuse3 packages that can't be parallel-installed, despite upstream explicitly renamed fusermount to fusermount3 so that was possible [1].
Now, I'm not sure if the fusermount (symlinked to fusermount3) tool we provide is backward compatible with the mounts that may be created using legacy libfuse, so I think is an aspect to check deeply (it may be just a false alarm, but better to check again).
One aspect that I didn't check fully, but that worries me a bit is how can preserve fuse and fuse3 to be installed together (as some out-archive components such as virtual machine additions or other pre-compiled binaries may still depend on libfuse and fusermount).
Now, this is not a problem for the library, but it is for the fuse/fuse3 packages that can't be parallel-installed, despite upstream explicitly renamed fusermount to fusermount3 so that was possible [1].
Now, I'm not sure if the fusermount (symlinked to fusermount3) tool we provide is backward compatible with the mounts that may be created using legacy libfuse, so I think is an aspect to check deeply (it may be just a false alarm, but better to check again).
[1] https:/ /github. com/libfuse/ libfuse/ releases/ tag/fuse- 3.0.0