Hi Helmut, On Thu, Nov 2, 2023 at 12:15 PM Helmut Grohne <hel...@subdivi.de> wrote: > I have a slightly unusual request. I know libfuse 2.x is a legacy in > maintenance mode slated for removal eventually. Unfortunately, 2/3 of > fuse users still use the 2.x branch so it seems like we will have to > support it a bit longer than expected. I think distributions should do the opposite, somehow enforce projects to migrate to the new, supported FUSE version. Basically it is deprecated since 2018 and as 2024 is approaching it means for six years.
> Unfortunately, this currently requires fuse >= 3.3 and e.g. fuse2fs from > e2fsprogs still uses fuse 2.x. Last time Ted Ts'o was inquired about > porting to 3.x, he was unenthusiastic and when I spent a look, it is > quite non-trivial as the API changed a lot. It's not just fuse2fs that > is affected but still 2/3 of drivers. [...] > So I think we should backport this into fuse 2.x. This is not to say > that we should stop porting drivers to the 3.x API. It also slightly > improves compatibility between 2.x and 3.x, so that seems like a sane > trade-off to me. Do you agree? Yes, it makes upstreams more easily staying with the FUSE 2 API. Making the switch to the FUSE 3 API more difficult. But OK, let it go. I'm preparing the upload. Regards, Laszlo/GCS
