Hello,
I am planning on updating libfuse from version 2.9.9 to 3.4.2. Currently, we have both libfuse2 (source fuse-2.9.9 or just fuse) and libfuse3 (source fuse-3.4.2 or fuse3). It would be nice if all users would move from libfuse2 to libfuse3.
What would be the best method to accomplish this: 1. Simply update fuse to fuse-3.4.2 2. Mark fuse 3.4.2 as obsoletes fuse < 3, and ship both for a while 3. Any other method
I am afraid we will break depending applications if we choose 1, though it should be compatible.
On Friday 2019-03-29 19:54, Goldwyn Rodrigues wrote:
Hello,
I am planning on updating libfuse from version 2.9.9 to 3.4.2. Currently, we have both libfuse2 (source fuse-2.9.9 or just fuse) and libfuse3 (source fuse-3.4.2 or fuse3). It would be nice if all users would move from libfuse2 to libfuse3.
What would be the best method to accomplish this:
0. In a home project, check that all fuse users actually build with the fuse 3.x API and none fail. 0. If fuse 2.x is still needed, move fuse to fuse2 (everybody failed to heed the packaging guidelines level when introducing fuse3, me included) 0. copying fuse3 into the fuse dir.
- Simply update fuse to fuse-3.4.2
On 20:15 29/03, Jan Engelhardt wrote:
On Friday 2019-03-29 19:54, Goldwyn Rodrigues wrote:
Hello,
I am planning on updating libfuse from version 2.9.9 to 3.4.2. Currently, we have both libfuse2 (source fuse-2.9.9 or just fuse) and libfuse3 (source fuse-3.4.2 or fuse3). It would be nice if all users would move from libfuse2 to libfuse3.
What would be the best method to accomplish this:
- In a home project, check that all fuse users actually build with the fuse 3.x API and none fail.
- If fuse 2.x is still needed, move fuse to fuse2 (everybody failed to heed the packaging guidelines level when introducing fuse3, me included)
- copying fuse3 into the fuse dir.
Okay I tried working on this. However, fuse2 header files etc. are called fuse.h wheras fuse3 has fuse3.h. Renaming the files is probably not a good idea for conflicts. It would be better to use the applications to use fuse3 instead of fuse by pointing the code to use fuse3.h instead.
As for other distros, all maintain both fuse and fuse3 like we do now.
-
Goldwyn Rodrigues -
Jan Engelhardt