From: Nikolaus R. <Nik...@ra...> - 2016-02-09 17:58:31
|
On Feb 09 2016, Luca Risolia <luc...@pu...> wrote: > On 09/02/2016 10:42, Jean-Pierre André wrote: >> In other words, projects relying on libfuse2 are going >> to be deprecated... > > I am worried. Could you please *clearly state* what libfuse3 is going to > break in terms of API and ABI? To be certain, you have to compare the codes. Miklos started libfuse3 several years ago, and I don't think there's a definitive record of the changes. Some things that I remember: * readdirplus support * some datatypes changed (e.g. fuse_ino_t now has the same type as ino_t) I was also pretty sure that FUSE3 no longer uses the entire channel abstraction (struct fuse_chan) because FUSE only ever used just one channel. But looking at fuse_lowlevel.h, it's actually still present. I should look into that... Best, -Nikolaus (No Cc on replies please, I'm reading the list) -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« |