dps: gl-setup may have to create ~/.ssh and touch the authkeys file...

I've been unwilling to create the authkeys file if it does not already
exist, because it represents a significant change in accessibility for
that account.

However, in the "distro package" scenario, one wants to make it as easy
as possible for the end-user (who is actually an admin for the gitolite
being hosted on his account, let's not forget) to use.

And it seems that in some cases that might mean he does not (yet) have a
~/.ssh even...

src/gl-setup

@@ -52,6 +52,15 @@ else
     cp $GL_PACKAGE_CONF/example.gitolite.rc ~/.gitolite.rc
 fi
 
+# setup ssh stuff.  We break our normal rule that we will not fiddle with
+# authkeys etc., because in this case it seems appropriate
+cd
+mkdir -p .ssh
+touch .ssh/authorized_keys
+chmod go-w . .ssh .ssh/authorized_keys
+
+# now we get to gitolite itself
+
 gl-install -q
 
 GL_ADMINDIR=$(cd;perl -e 'do ".gitolite.rc"; print $GL_ADMINDIR')