notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Remember
I remember
2024-11-06 Today brought in a new category: filesystems. Sadly, the website did not process it well. I am working on that. It may take a few days.
2024-11-07 Commit processing is halted. I have a fix for the new category. It is making its way through the system.
UPDATE: the backend is processing the original filesystems commit now. It should take about an hour.
UPDATE: as of 20:30 UTC, the filesystems commit has been processed. Commit processing is now up to date.
Port details
s3backer FUSE filesystem that uses Amazon S3 as a backing store
1.5.4_1 filesystemsnew! on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one.
Maintainer: bsdports@staktrace.com search for ports maintained by this maintainer
Port Added: 2024-11-07 19:52:55
Last Update: 2024-11-06 15:17:35
Commit Hash: 6e2da96
License: GPLv2
WWW:
https://github.com/archiecobbs/s3backer
Description:
s3backer is a filesystem that contains a single file backed by the Amazon Simple Storage Service (Amazon S3). As a filesystem, it is very simple: it provides a single normal file having a fixed size. Underneath, the file is divided up into blocks, and the content of each block is stored in a unique Amazon S3 object. In other words, what s3backer provides is really more like an S3-backed virtual hard disk device, rather than a filesystem. In typical usage, a normal filesystem is mounted on top of the file exported by the s3backer filesystem using a loopback mount (or disk image mount on Mac OS X). By not attempting to implement a complete filesystem, which is a complex undertaking and difficult to get right, s3backer can stay very lightweight and simple. Only three HTTP operations are used: GET, PUT, and DELETE. All of the experience and knowledge about how to properly implement filesystems that already exists can be reused. By utilizing existing filesystems atop s3backer, you get full UNIX filesystem semantics. Subtle bugs or missing functionality relating to hard links, extended attributes, POSIX locking, etc. are avoided.
Homepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
Expand this list (13 items)
Collapse this list.
  1. /usr/local/share/licenses/fusefs-s3backer-1.5.4_1/catalog.mk
  2. /usr/local/share/licenses/fusefs-s3backer-1.5.4_1/LICENSE
  3. /usr/local/share/licenses/fusefs-s3backer-1.5.4_1/GPLv2
  4. bin/s3backer
  5. share/man/man1/s3backer.1.gz
  6. share/doc/packages/s3backer/CHANGES
  7. share/doc/packages/s3backer/COPYING
  8. share/doc/packages/s3backer/INSTALL
  9. share/doc/packages/s3backer/README
  10. share/doc/packages/s3backer/TODO
  11. @owner
  12. @group
  13. @mode
Collapse this list.
Dependency lines:
  • fusefs-s3backer>0:filesystems/s3backer
To install the port:
cd /usr/ports/filesystems/s3backer/ && make install clean
To add the package, run one of these commands:
  • pkg install filesystems/s3backer
  • pkg install fusefs-s3backer
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
PKGNAME: fusefs-s3backer
Flavors: there is no flavor information for this port.
distinfo:
TIMESTAMP = 1584785989 SHA256 (s3backer-1.5.4.tar.gz) = 7e73bb8378a4ccf7b1904a078fbc4731b07138951cbe1c20ce7aa0eb3e8da0d0 SIZE (s3backer-1.5.4.tar.gz) = 201362

Packages (timestamps in pop-ups are UTC):
fusefs-s3backer
ABIaarch64amd64armv6armv7i386powerpcpowerpc64powerpc64le
FreeBSD:13:latest--------
FreeBSD:13:quarterly--------
FreeBSD:14:latest--------
FreeBSD:14:quarterly--------
FreeBSD:15:latest-1.5.4_1n/a-n/a---
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. pkgconf>=1.3.0_1 : devel/pkgconf
Library dependencies:
  1. libcurl.so : ftp/curl
  2. libexpat.so : textproc/expat2
  3. libfuse.so : filesystems/fusefs-libs
There are no ports dependent upon this port

Configuration Options:
No options to configure
Options name:
filesystems_s3backer
USES:
fuse pkgconfig ssl
FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (1 items)
Collapse this list.
  1. https://s3.amazonaws.com/archie-public/s3backer/
Collapse this list.
Port Moves

Number of commits found: 1

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
1.5.4_1
06 Nov 2024 15:17:35
commit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9d files touched by this commit
Robert Clausecker (fuz) search for other commits by this committer
filesystems: add new category for file systems and related utilities

The filesystems category houses file systems and file system utilities.
It is added mainly to turn the sysutils/fusefs-* pseudo-category into
a proper one, but is also useful for the sundry of other file systems
related ports found in the tree.

Ports that seem like they belong there are moved to the new category.
Two ports, sysutils/fusefs-funionfs and sysutils/fusefs-fusepak are
not moved as they currently don't fetch and don't have TIMESTAMP set
in their distinfo, but that is required to be able to push a rename
of the port by the pre-receive hook.

Approved by:	portmgr (rene)
Reviewed by:	mat
Pull Request:	https://github.com/freebsd/freebsd-ports/pull/302
PR:		281988

Number of commits found: 1