svn commit: r475634 - in head/sysutils: . fusefs-s3backer
Kurt Jaeger
pi at FreeBSD.org
Sun Jul 29 09:00:19 UTC 2018
Author: pi
Date: Sun Jul 29 09:00:17 2018
New Revision: 475634
URL: https://svnweb.freebsd.org/changeset/ports/475634
Log:
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 at staktrace.com>
Added:
head/sysutils/fusefs-s3backer/
head/sysutils/fusefs-s3backer/Makefile (contents, props changed)
head/sysutils/fusefs-s3backer/distinfo (contents, props changed)
head/sysutils/fusefs-s3backer/pkg-descr (contents, props changed)
head/sysutils/fusefs-s3backer/pkg-plist (contents, props changed)
Modified:
head/sysutils/Makefile
Modified: head/sysutils/Makefile
==============================================================================
--- head/sysutils/Makefile Sun Jul 29 08:55:06 2018 (r475633)
+++ head/sysutils/Makefile Sun Jul 29 09:00:17 2018 (r475634)
@@ -396,6 +396,7 @@
SUBDIR += fusefs-ntfs-compression
SUBDIR += fusefs-pod
SUBDIR += fusefs-rar2fs
+ SUBDIR += fusefs-s3backer
SUBDIR += fusefs-s3fs
SUBDIR += fusefs-simple-mtpfs
SUBDIR += fusefs-smbnetfs
Added: head/sysutils/fusefs-s3backer/Makefile
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/sysutils/fusefs-s3backer/Makefile Sun Jul 29 09:00:17 2018 (r475634)
@@ -0,0 +1,25 @@
+# $FreeBSD$
+
+PORTNAME= s3backer
+DISTVERSION= 1.5.0
+CATEGORIES= sysutils
+MASTER_SITES= https://s3.amazonaws.com/archie-public/s3backer/
+PKGNAMEPREFIX= fusefs-
+
+MAINTAINER= bsdports at staktrace.com
+COMMENT= FUSE filesystem that uses Amazon S3 as a backing store
+
+LICENSE= GPLv2
+LICENSE_FILE= ${WRKSRC}/COPYING
+
+LIB_DEPENDS= libcurl.so:ftp/curl \
+ libexpat.so:textproc/expat2
+
+GNU_CONFIGURE= 1
+# Need to have curl/curl.h on the include path. Is there a better
+# way to do this than sending CPPFLAGS to configure?
+CONFIGURE_ARGS= CPPFLAGS="-I${LOCALBASE}/include"
+
+USES= fuse pkgconfig ssl
+
+.include <bsd.port.mk>
Added: head/sysutils/fusefs-s3backer/distinfo
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/sysutils/fusefs-s3backer/distinfo Sun Jul 29 09:00:17 2018 (r475634)
@@ -0,0 +1,3 @@
+TIMESTAMP = 1532313795
+SHA256 (s3backer-1.5.0.tar.gz) = 82d93c54acb1e85828b6b80a06e69a99c7e06bf6ee025dac720e980590d220d2
+SIZE (s3backer-1.5.0.tar.gz) = 192317
Added: head/sysutils/fusefs-s3backer/pkg-descr
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/sysutils/fusefs-s3backer/pkg-descr Sun Jul 29 09:00:17 2018 (r475634)
@@ -0,0 +1,24 @@
+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
Added: head/sysutils/fusefs-s3backer/pkg-plist
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/sysutils/fusefs-s3backer/pkg-plist Sun Jul 29 09:00:17 2018 (r475634)
@@ -0,0 +1,7 @@
+bin/s3backer
+man/man1/s3backer.1.gz
+share/doc/packages/s3backer/CHANGES
+share/doc/packages/s3backer/COPYING
+share/doc/packages/s3backer/INSTALL
+share/doc/packages/s3backer/README
+share/doc/packages/s3backer/TODO
More information about the svn-ports-head
mailing list