CVE and update status of the FreeBSD ports tree3,295 unaddressed CVEs in 670 portsAll times are CET
Port details

sysutils/fusefs-s3backer

Moved to filesystems/s3backer on : Moved to new category filesystems

This port is no longer in the ports tree, its history is kept below.

Links
cgit

Commits (8)

Robert Clausecker (fuz)
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
6e2da9672f
Muhammad Moinur Rahman (bofh) · 1.5.4_1
sysutils/fusefs-s3backer: Moved man to share/man

Approved by:    portmgr (blanket)
d6f1c5875c
Stefan Eßer (se) · 1.5.4
Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)
fb16dfecae
Stefan Eßer (se) · 1.5.4
Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)
b7f05445c0
Mathieu Arnold (mat) · 1.5.4
One more small cleanup, forgotten yesterday. Reported by:	lwhsu
cf118ccf87
Mathieu Arnold (mat) · 1.5.4
Remove # $FreeBSD$ from Makefiles.
305f148f48
Li-Wen Hsu (lwhsu) · 1.5.4
- Update to 1.5.4

PR:		244946
Submitted by:	maintainer
b3f77acdb8
Kurt Jaeger (pi) · 1.5.0
New port: sysutils/fusefs-s3backer

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.

WWW: https://github.com/archiecobbs/s3backer

PR:		229998
Submitted by:	Kartikaya Gupta <bsdbugs@staktrace.com>
8ddc0f1be0