François Degros

I don't know if the behavior of `archive_error_string()` is explicitly specified. But from the way the `libarchive` API is designed, I would expect the following behavior. After a `libarchive` function...

With the truncated `.gz` provided by @vassilit, it is actually the `archive_read_open1()` function that returns `ARCHIVE_FATAL` (-30), instead of `archive_read_next_header()`. In this case, `archive_error_string()` also returns a null pointer after...

The issue is still there in `libarchive` 3.8.0. Reproduced with tests in https://github.com/fdegros/libarchive/tree/compress_support: ``` $ gdb --args ./libarchive_test test_read_append_compress_filter (gdb) run Starting program: /usr/local/google/home/fdegros/libarchive/libarchive_test test_read_append_compress_filter [Thread debugging using libthread_db enabled]...

I'm not sure what exactly this feature request is about. If the feature you have in mind is implemented, what does it change concretely for a `fuse-archive` user? What would...

Sorry, but I still don't understand. Could you please explain what you exactly mean by: > working with archives and supporting random-access seek without modifying existing user's scripts/code" What does...

> I just found a repo which implements an adapter which lets one use LD_PRELOAD for FUSE-based file systems without FUSE kernel module: https://github.com/sholtrop/ldpfuse Thanks. I see. That's good to...

Thanks for this feature request. I think I understand what it is about. However, I'm going to close it. At its heart, `fuse-archive` is a [FUSE](https://en.wikipedia.org/wiki/Filesystem_in_Userspace)-based file system and I'm...

Thanks for your interest in `mount-zip`. I haven't looked at FUSE 3, and I don't really have a business need for it at the moment. So I don't know how...

The migration to FUSE 3 is now complete. I will release an official version of `mount-zip` shortly.

[`mount-zip` 1.8](https://github.com/google/mount-zip/releases/tag/v1.8) uses FUSE 3 by default.