at 22.05-pre 55 lines 1.8 kB view raw
1{ fetchFromGitHub, git, gnupg, makeWrapper, openssl, lib, stdenv 2, libxslt, docbook_xsl 3}: 4 5stdenv.mkDerivation rec { 6 pname = "git-crypt"; 7 version = "0.6.0"; 8 9 src = fetchFromGitHub { 10 owner = "AGWA"; 11 repo = pname; 12 rev = version; 13 sha256 = "13m9y0m6gc3mlw3pqv9x4i0him2ycbysizigdvdanhh514kga602"; 14 }; 15 16 nativeBuildInputs = [ libxslt makeWrapper ]; 17 18 buildInputs = [ openssl ]; 19 20 patchPhase = '' 21 substituteInPlace commands.cpp \ 22 --replace '(escape_shell_arg(our_exe_path()))' '= "git-crypt"' 23 ''; 24 25 makeFlags = [ 26 "PREFIX=${placeholder "out"}" 27 "ENABLE_MAN=yes" 28 "DOCBOOK_XSL=${docbook_xsl}/share/xml/docbook-xsl-nons/manpages/docbook.xsl" 29 ]; 30 31 postFixup = '' 32 wrapProgram $out/bin/git-crypt --prefix PATH : $out/bin:${git}/bin:${gnupg}/bin 33 ''; 34 35 meta = with lib; { 36 homepage = "https://www.agwa.name/projects/git-crypt"; 37 description = "Transparent file encryption in git"; 38 longDescription = '' 39 git-crypt enables transparent encryption and decryption of files in a git 40 repository. Files which you choose to protect are encrypted when 41 committed, and decrypted when checked out. git-crypt lets you freely 42 share a repository containing a mix of public and private 43 content. git-crypt gracefully degrades, so developers without the secret 44 key can still clone and commit to a repository with encrypted files. This 45 lets you store your secret material (such as keys or passwords) in the 46 same repository as your code, without requiring you to lock down your 47 entire repository. 48 ''; 49 downloadPage = "https://github.com/AGWA/git-crypt/releases"; 50 license = licenses.gpl3; 51 maintainers = [ maintainers.dochang ]; 52 platforms = platforms.unix; 53 }; 54 55}