François Degros

Thanks Matteo for your detailed bug report. I confirm that hard links are not properly handled by `fuse-archive`. The proposed pull request #11 does not solve the issue, at least...

Since `fuse-archive` is built on top of `libarchive`, this feature request might be a feature request for `libarchive`.

By default, `fuse-archive` now works in fully cached mode. See [documentation](https://github.com/google/fuse-archive/blob/main/README.md#caching). I don't think there is a need to use a third-party tool in order to scan and index a...

I don't really know what's involved in getting a package into a Linux distribution, and this is not my priority at the moment. If you know how to do it,...

See also https://mentors.debian.net/package/mount-zip/

> Some archive formats can have entries that lack filenames. So it makes sense that you would get NULL when querying the pathname. Having said that, it looks like this...

> I just published a new patch release. This is the first attempt doing a release entirely from the GitHub interface. Thus keep me informed if the automatically attached assets...

I also created a [pull request](https://github.com/gentoo/gentoo/pull/37316) to upgrade `rar2fs` to 1.29.7 in Gentoo. We'll see how it goes...

Thanks for the feature request. Your assessment is correct. `fuse-archive` currently doesn't try to convey the sparseness of files stored in archives. Doing so is certainly possible. But I don't...

The [`lseek` callback](https://libfuse.github.io/doxygen/structfuse__operations.html#a957953a38415bf11c36db9e255f16941) was added to FUSE 3, and it is not present in FUSE 2. As a consequence, this feature request depends on https://github.com/google/fuse-archive/issues/16.