Package Details: mergerfs 2.31.0-1

Git Clone URL: https://aur.archlinux.org/mergerfs.git (read-only, click to copy)
Package Base: mergerfs
Description: FUSE based union filesystem
Upstream URL: https://github.com/trapexit/mergerfs
Keywords: filesystem fuse
Licenses: custom:ISC
Submitter: pheerai
Maintainer: willemw
Last Packager: willemw
Votes: 23
Popularity: 1.11
First Submitted: 2015-10-23 12:47
Last Updated: 2020-10-02 16:58

Dependencies (2)

Required by (1)

Sources (1)

Latest Comments

1 2 3 Next › Last »

willemw commented on 2020-03-25 00:08

@Sparticuz:

My point was that it is not necessary to extend "arch" in order to build on ARM.

Even ArchLinuxARM themselves don't do it for their own repository packages. Not even for modified PKGBUILD files specific for ARM (https://github.com/archlinuxarm/PKGBUILDs).

Sparticuz commented on 2020-03-24 23:57

@willemw I think what @cryzed is saying is that it builds just fine on arm, so adding arm would allow the package to be built on arm. In fact, looking at debians package, they have a bunch of different Arch's. https://packages.debian.org/stretch/utils/mergerfs ... Unless I'm missing something?

willemw commented on 2020-03-24 23:40

@cryzed:

"any" will create a ...-any.pkg.tar.zst package file, which you can install on any platform. Used for installing script files, which are portable.

"x86_64" will create a ...-x86_64.pkg.tar.zst package file, which you can only install on a x86_64 platform. Used for compiled packages, which are only binary compatible with a specific platform.

willemw commented on 2020-03-24 23:19

@cryzed:

I prefer not to extent the "arch" array. Most packages, that are compiled, don't do that (otherwise it would mean updating a lot of PKGBUILD files).

You can use "makepkg --ignorearch" (indirectly through an AUR helper) to build packages on other platforms. ArchLinuxARM even used to mention this in their Wiki.

Extending the "arch" array is, for example, useful for *-bin packages.

cryzed commented on 2020-03-24 23:02

@willemw thanks, but what about extending the arch array?

willemw commented on 2020-03-24 20:22

@cryzed: Thanks. Added fuse2.

cryzed commented on 2020-03-24 20:12

You should define fuse2 as an optional dependency, it's needed to get mergerfs to work with /etc/fstab. Also I tested this successfully on a Raspberry Pi 4, the architecture armv7h can be added to the arch array.

moonman commented on 2019-06-29 00:50

@willemw I just did https://github.com/trapexit/mergerfs/issues/647 But kinda wanted to get some feedback here, maybe it is specific to my setup?

willemw commented on 2019-06-28 05:59

@moonman: Have you reported this upstream?

moonman commented on 2019-06-28 03:25

This is corrupting files for me.

Fine: source -> directly to pool member(bypassing mergerfs).

Corrupt: source -> mergerfs pool

Fine: source -> mhddfs pool (same hdd pool, mergerfs disabled, mhddfs enabled)

Tested with a 60GB video file and diff several times and different mount options.