Open terencehonles opened 6 years ago
@terencehonles extremely well structured code ;) The changes between both versions are subtle but also quite significant. First, the mechanism of how a FUSE filessystem is started has been changed, which I guess is the smaller problem. Second, the parameter definitions of a lot of calls have been changed, eliminating some inconsistencies found in libfuse2 (ignoring the fact that some calls, which were already marked as deprecated, have been removed). From fusepy's perspective, it would require at least two versions of the fuse_operations
and fuse_lowlevel_ops
structure types and potentially also two versions each of the FUSE
and FUSELL
classes. Working with if
-else
-blocks for handling the differences within a single FUSE
class for instance looks like ... hard to debug and maintain, for me at least.
What will it take to be able to support both libfuse2 and libfuse3?