From a454111d32753a60cc909b88fe7738eeed41f532 Mon Sep 17 00:00:00 2001
From: Sitaram Chamarty <sitaram@atc.tcs.com>
Date: Thu, 21 Jun 2012 05:29:14 +0530
Subject: [PATCH] repo-specific umask

manually smoke tested but should be fine
---
 src/lib/Gitolite/Triggers/RepoUmask.pm | 54 ++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 src/lib/Gitolite/Triggers/RepoUmask.pm

diff --git a/src/lib/Gitolite/Triggers/RepoUmask.pm b/src/lib/Gitolite/Triggers/RepoUmask.pm
new file mode 100644
index 0000000..b0a9ad1
--- /dev/null
+++ b/src/lib/Gitolite/Triggers/RepoUmask.pm
@@ -0,0 +1,54 @@
+package Gitolite::Triggers::RepoUmask;
+
+use Gitolite::Rc;
+use Gitolite::Common;
+use Gitolite::Conf::Load;
+
+use strict;
+use warnings;
+
+# setting a repo specific umask
+# ----------------------------------------------------------------------
+
+=for usage
+
+  * In the rc file, add 'RepoUmask::pre_git' and 'RepoUmask::post_create' to
+    the corresponding trigger lists.
+
+  * For each repo that is to get a different umask than the default, add a
+    line like this:
+
+        option umask = 0027
+
+=cut
+
+# sadly option/config values are not available at pre_create time for normal
+# repos.  So we have to do a one-time fixup in a post_create trigger.
+sub post_create {
+    my $repo = $_[1];
+
+    my $umask = option($repo, 'umask');
+    _chdir($rc{GL_REPO_BASE});  # because using option() moves us to ADMIN_BASE!
+
+    return unless $umask;
+
+    # unlike the one in the rc file, this is a string
+    $umask = oct($umask);
+    my $mode = "0" . sprintf("%o", $umask ^ 0777);
+
+    system("chmod -R $mode $repo.git >&2");
+}
+
+sub pre_git {
+    my $repo = $_[1];
+
+    my $umask = option($repo, 'umask');
+    _chdir($rc{GL_REPO_BASE});  # because using option() moves us to ADMIN_BASE!
+
+    return unless $umask;
+
+    # unlike the one in the rc file, this is a string
+    umask oct($umask);
+}
+
+1;