Bug 229998 - [NEW PORT]: Add s3backer as a port
Summary: [NEW PORT]: Add s3backer as a port
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-24 00:45 UTC by Kartikaya Gupta
Modified: 2018-07-29 09:01 UTC (History)
1 user (show)

See Also:


Attachments
s3backer port (4.47 KB, patch)
2018-07-24 00:45 UTC, Kartikaya Gupta
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kartikaya Gupta 2018-07-24 00:45:39 UTC
Created attachment 195406 [details]
s3backer port

I'd like to add s3backer [1] to the ports collection. I built the port per the instructions in the porting handbook. The .diff file is attached. Please let me know what the next steps are with respect to getting this added. Thanks!

[1] https://github.com/archiecobbs/s3backer
Comment 1 Kurt Jaeger freebsd_committer freebsd_triage 2018-07-29 09:00:25 UTC
Committed, thanks!
Comment 2 commit-hook freebsd_committer freebsd_triage 2018-07-29 09:01:16 UTC
A commit references this bug:

Author: pi
Date: Sun Jul 29 09:00:18 UTC 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@staktrace.com>

Changes:
  head/sysutils/Makefile
  head/sysutils/fusefs-s3backer/
  head/sysutils/fusefs-s3backer/Makefile
  head/sysutils/fusefs-s3backer/distinfo
  head/sysutils/fusefs-s3backer/pkg-descr
  head/sysutils/fusefs-s3backer/pkg-plist