I have no problems with installing the package, but while looking through the PKGBUILD after the last update, I stumbled across the httpdirfs --cache
flag and the comment about it.
In short, with this flag httpdirfs caches all downloaded data in the user's cache directory permanently, using sparse allocation for partially downloaded files (as is here the case for the ISO). In the project's GitHub repo it is also mentioned that initial download speeds could be limited to 15 MiB/s due to the feature's implementation.
While I don't think the speed is a concern with a download size of ~400 MiB (I surely wouldn't notice), we really don't gain anything from the caching. When the package is updated, the cached ISO won't speed anything up since a new ISO with a new name will have to be downloaded freshly from Microsoft. Besides that it just piles up in the user's home dir, with every new ISO occupying about 6 GiB (mostly pre-allocated) space. I'd like to suggest possible changes:
-
Just removing the
--cache
option altogether, possibly mentioning why it's not used anymore in the build instructions. -
Using the
--cache-location
option alongside to point to the $srcdir (typically src/). This way, the user's choice where to save source files is honored, and the cached files can be cleaned up easily withmakepkg --clean
or--cleanbuild
.
Pinned Comments
kode54 commented on 2024-02-04 10:43 (UTC) (edited on 2025-05-20 21:47 (UTC) by kode54)
You apparently need to be a member of the
disk
group to mount a filesystem as an otherwise unprivileged user.And log out and back in again.
Edit: If you experience weird missing dependency issues with
fuse3
orgumbo-parser
, you need to rebuildhttpdirfs
.rebuild-detector
, which suppliescheckrebuild
and a pacman hook which also runs it during upgrades, can somewhat alleviate the problem of keeping AUR packages up to date, since they're not usually bumped when they need a rebuild.