[fuse-devel] Re: FBSD patches reworked

[Miklos S. <mi...@sz...>]

> > Could do that.  I'll add a #warning to fuse.h about deprecated API
> > being used. 
> 
> Btw, why do you always (?) set the default to an older API? 

To be source compatible with all 2.X based filesystems (2.1 didn't yet
have FUSE_USE_VERSION).

> > These are not really wild refactorizations, but minor things like the
> > statfs -> statvfs change.
> 
> Well, maybe I was doing too much fuss about this... But I like that
> "migration guide" idea, let me elaborate more on it.

The only problem with this is that I'm too lazy to do it, unless I
people actually have problems doing the migration.  To date there
hasn't been any problems AFAIK, so I don't want waste time on it.

> > Migrating should be trivial in most cases:
> > 
> >   - define FUSE_USE_VERSION to 25
> >   - compile
> >   - fix errors and warnings
> 
> Yes, that's when you move from 24 to 25. Yet your decision ditches
> backward compatibily on FBSD not only with API 24, but with many APIs
> back to 11. (I actually tried to use an fs with API 11...)

Compatibility with version 11 was only provided as a stepping stone to
porting to 2.X.  It doesn't even provide full API compatibility.

Added '#warning' for this case.

> Now if you summarized me in your reply how to migrate the code from
> API 11 to 25, that would be pretty much lost in the mail archives.
> 
> That's why I speak of that "migration guide", or better said, "API
> Changelog". An easy to find document which makes the whole picture clear.

Every API change should be in the Changelog, I'll try to mark these
more consistently in the future.

Miklos