Package Details: juicefs 4.3.8-1

Git Clone URL: (read-only, click to copy)
Package Base: juicefs
Description: A shared POSIX file system for the cloud
Upstream URL:
Keywords: cloudstorage filesystem fuse
Licenses: custom
Submitter: Sasasu
Maintainer: Sasasu
Last Packager: Sasasu
Votes: 1
Popularity: 0.000000
First Submitted: 2018-12-30 16:28 (UTC)
Last Updated: 2020-10-06 09:39 (UTC)

Required by (0)

Sources (1)

Latest Comments

arnottcr commented on 2021-07-06 21:16 (UTC) (edited on 2021-07-06 22:30 (UTC) by arnottcr)

I find the name sharing problematic, but this package should be renamed to juicefs-bin. it is not built from source.

I am interested in building juicefs from source, so -bin and -git are neither accurate nor desired. would you prefer juicefs, go-juicefs, foss-juicefs, juicefs-fuse, or something else?

Sasasu commented on 2021-07-06 06:27 (UTC)

do both tools rely upon the same name: "juicefs"?

Yes. and this is the same company with the same author.

Sasasu commented on 2021-07-06 06:16 (UTC)

for axolotl: this is the close source version juicefs, it is a paid service. if you want the opensource version, please create a juicefs-bin or juicefs-git to provide. the opensource version is very sample. S3FS even better than it.

arnottcr commented on 2021-07-06 06:14 (UTC) (edited on 2021-07-06 06:14 (UTC) by arnottcr)

so, do both tools rely upon the same name: "juicefs"? I am looking to package the go tooling, but this appears to squat on the same name.

Sasasu commented on 2021-06-11 11:50 (UTC)


this is the closesource juicefs, not the opensource version.

The metadata using a private protocol and using S3 API to store the data. and this software is not free

the binary file is a bash (and python) script. it will download the real juicefs to ~/.juicefs/jfsmount

arnottcr commented on 2021-06-11 07:35 (UTC) (edited on 2021-06-11 07:36 (UTC) by arnottcr)

a few notes: - since you are downloading a static file, this constitutes a binary package, thus juicefs-bin would be the proper package name - I am very unclear where 4.3.8 is coming from, since github shows 0.14.2 as latest release - it appears this version is unmoored from the artefact url, as such when a new version is released, will this silently break?