From owner-svn-ports-head@freebsd.org Sun Feb 5 21:21:19 2017 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2F9ACD2AC5; Sun, 5 Feb 2017 21:21:19 +0000 (UTC) (envelope-from ashish@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B097A73; Sun, 5 Feb 2017 21:21:19 +0000 (UTC) (envelope-from ashish@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v15LLIdc082601; Sun, 5 Feb 2017 21:21:18 GMT (envelope-from ashish@FreeBSD.org) Received: (from ashish@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v15LLI9a082597; Sun, 5 Feb 2017 21:21:18 GMT (envelope-from ashish@FreeBSD.org) Message-Id: <201702052121.v15LLI9a082597@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ashish set sender to ashish@FreeBSD.org using -f From: Ashish SHUKLA Date: Sun, 5 Feb 2017 21:21:18 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r433457 - in head/security: . git-crypt X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2017 21:21:19 -0000 Author: ashish Date: Sun Feb 5 21:21:18 2017 New Revision: 433457 URL: https://svnweb.freebsd.org/changeset/ports/433457 Log: git-crypt enables transparent encryption and decryption of files in a git repository. Files which you choose to protect are encrypted when committed, and decrypted when checked out. git-crypt lets you freely share a repository containing a mix of public and private content. git-crypt gracefully degrades, so developers without the secret key can still clone and commit to a repository with encrypted files. This lets you store your secret material (such as keys or passwords) in the same repository as your code, without requiring you to lock down your entire repository. WWW: https://www.agwa.name/projects/git-crypt/ Added: head/security/git-crypt/ head/security/git-crypt/Makefile (contents, props changed) head/security/git-crypt/distinfo (contents, props changed) head/security/git-crypt/pkg-descr (contents, props changed) Modified: head/security/Makefile Modified: head/security/Makefile ============================================================================== --- head/security/Makefile Sun Feb 5 21:20:24 2017 (r433456) +++ head/security/Makefile Sun Feb 5 21:21:18 2017 (r433457) @@ -164,6 +164,7 @@ SUBDIR += gag SUBDIR += gcipher SUBDIR += gcr + SUBDIR += git-crypt SUBDIR += gnome-gpg SUBDIR += gnome-keyring SUBDIR += gnome-keyring-sharp Added: head/security/git-crypt/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/security/git-crypt/Makefile Sun Feb 5 21:21:18 2017 (r433457) @@ -0,0 +1,43 @@ +# Created by: Ashish SHUKLA +# $FreeBSD$ + +PORTNAME= git-crypt +PORTVERSION= 0.5.0 +CATEGORIES= security +MASTER_SITES= https://www.agwa.name/projects/git-crypt/downloads/ \ + LOCAL/ashish/ + +MAINTAINER= ashish@FreeBSD.org +COMMENT= Transparent file encryption in git + +LICENSE= GPLv3 +LICENSE_FILE= ${WRKSRC}/COPYING + +RUN_DEPENDS= git:devel/git \ + gpg:security/gnupg + +OPTIONS_DEFINE= DOCS + +LDFLAGS+= -L${OPENSSLLIB} +MAKE_ENV+= PREFIX=${PREFIX} "CXXFLAGS=${CXXFLAGS}" \ + "LDFLAGS=${LDFLAGS}" + +DOCS_BUILD_DEPENDS= xsltproc:textproc/libxslt \ + docbook-xsl>=0:textproc/docbook-xsl +DOCS_MAKE_ARGS= ENABLE_MAN=yes \ + MANDIR=${MANPREFIX}/man \ + DOCBOOK_XSL=${LOCALBASE}/share/xsl/docbook/manpages/docbook.xsl +DOCS_PLIST_FILES= man/man1/${PORTNAME}.1.gz + +USES= gmake ssl + +PLIST_FILES= bin/${PORTNAME} + +post-extract: + @${GREP} -Rl '"gpg"' ${WRKSRC} |${XARGS} ${REINPLACE_CMD} -e 's,"gpg","${LOCALBASE}/bin/gpg",' + @${GREP} -Rl '"git"' ${WRKSRC} |${XARGS} ${REINPLACE_CMD} -e 's,"git","${LOCALBASE}/bin/git",' + +post-install: + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/git-crypt + +.include Added: head/security/git-crypt/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/security/git-crypt/distinfo Sun Feb 5 21:21:18 2017 (r433457) @@ -0,0 +1,3 @@ +TIMESTAMP = 1486329625 +SHA256 (git-crypt-0.5.0.tar.gz) = 0a8f92c0a0a125bf768d0c054d947ca4e4b8d6556454b0e7e87fb907ee17cf06 +SIZE (git-crypt-0.5.0.tar.gz) = 56412 Added: head/security/git-crypt/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/security/git-crypt/pkg-descr Sun Feb 5 21:21:18 2017 (r433457) @@ -0,0 +1,11 @@ +git-crypt enables transparent encryption and decryption of files in a +git repository. Files which you choose to protect are encrypted when +committed, and decrypted when checked out. git-crypt lets you freely +share a repository containing a mix of public and private +content. git-crypt gracefully degrades, so developers without the +secret key can still clone and commit to a repository with encrypted +files. This lets you store your secret material (such as keys or +passwords) in the same repository as your code, without requiring you +to lock down your entire repository. + +WWW: https://www.agwa.name/projects/git-crypt/