gl-system-install -- system-wide install program

(as if we didn't already have enough programs with the word "install" in
their names!)

Anyway, this does what an RPM or a DEB would do -- basically implement
the instructions in Appendix C of doc/0.

You can use this to do a system-wide install if your distro isn't as
smart, forward-looking, and uptodate as Fedora ;-)

Clone the repo somewhere, cd to it, and run, for example:

    sudo src/gl-system-install /usr/local/bin /var/gitolite/conf /var/gitolite/hooks

or something like that.  See doc/0 for details.  Run without arguments
for help.

conf/example.gitolite.rc

@@ -7,6 +7,13 @@
 # You do NOT need to know perl to edit the paths; it should be fairly
 # self-explanatory and easy to maintain perl syntax :-)
 
+# --------------------------------------
+# Do not uncomment these values unless you know what you're doing
+# $GL_PACKAGE_CONF = "";
+# $GL_PACKAGE_HOOKS = "";
+
+# --------------------------------------
+
 # --------------------------------------
 
 # this is where the repos go.  If you provide a relative path (not starting

doc/0-INSTALL.mkd

@@ -3,8 +3,7 @@
 [Update 2009-11-18: easy install now works from msysgit also!]
 
 Gitolite is somewhat unusual as far as "server" software goes -- every userid
-on the system is a potential "gitolite host" and can install his own version
+on the server is a potential "gitolite host".
-if he chooses to.
 
 This document tells you how to install gitolite.  After the install is done,
 you may want to see the [admin document][admin] for adding users, repos, etc.
@@ -63,9 +62,9 @@ The "system install / user setup" section describes this method.
 
 ### user install
 
-There is an easy install script that makes installing very easy for the common
+The `gl-easy-install` script makes installing very easy for this case.  **This
-case.  **This script will setup everything on the server, but you have to run
+script will setup everything on the server, but you have to run it on your
-it on your workstation, NOT on the server!**
+workstation, NOT on the server!**
 
 Assumptions/pre-requisites:
 
@@ -96,6 +95,11 @@ of what it is going to do, and no pauses unless absolutely needed.  However,
 if you're doing this for the first time or you appreciate knowing what it is
 actually doing, I suggest you skip the `-q`.
 
+A detailed transcript of an install done using this method can be found in
+[doc/7-install-transcript.mkd][7it].
+
+[7it]: http://github.com/sitaramc/gitolite/blob/pu/doc/7-install-transcript.mkd
+
 #### advantages over the older install methods
 
   * all ssh problems reduced to **just one pre-requisite**: enable ssh pubkey
@@ -136,21 +140,31 @@ opposed to merely creating one which did not exist) is best left to a human.
     *don't* have to know perl to do so, it's fairly easy to guess in this
     limited case.
 
+----
+
 ### system install / user setup
 
-In this mode a system administrator installs gitolite using the server's
+(Note: other than getting a public key from the admin's workstation,
-distro package mechanism (yum install, apt-get install, etc).
+everything in this mode of install happens on the server).
 
-Once this is done, you as a user must run a command like this (unlike in the
+In this mode, the software is first installed system-wide, then the user runs
-"user install" mode, this is done directly on the server):
+a command to set up the hosting, supplying a public key.
 
-    gl-setup yourname.pub
+The root user can **install the software system-wide**, using either a package
+(rpm, deb, etc.), or by using the `gl-system-install` script.  (Run the script
+without any arguments for a brief usage message.  If that's not clear enough,
+read Appendix C below for details.)
 
-where yourname.pub is a copy of a public key from your workstation.  The first
+A normal user can then **set up the hosting** by running a command like this:
-time you run this, it will create a "gitolite-admin" repo and populate it with
+
-the right configuration for whoever has the corresponding private key to
+    gl-setup adminname.pub
-clone and push it.  In other words, that person is the administrator for this
+
-particular gitolite instance.
+where adminname.pub is a copy of a public key from that user's workstation.
+
+The first time this is run, it will create a "gitolite-admin" repo and
+populate it with the right configuration for whoever has the corresponding
+private key to clone and push it.  In other words, that person is the
+administrator for this particular gitolite instance.
 
 If your system administrator upgrades gitolite itself, things will usually
 just work without any change; you should not have to do anything special.
@@ -168,7 +182,7 @@ them, expect trouble :-)
 
 #### multiple gitolite instances
 
-With this mode of install, it's easy to create multiple gitolite instances
+With this mode of install, it's trivial to create multiple gitolite instances
 (say one for each department, on some mega company-wide server).  You can even
 do this without giving shell access to the admins.  Here's an example with
 just two "departments", and their admins Alice and Bob:

src/gl-install

@@ -1,5 +1,7 @@
 #!/usr/bin/perl
 
+# INTERNAL COMMAND.  NOT MEANT TO BE RUN BY THE USER DIRECTLY.
+
 use strict;
 use warnings;
 

src/gl-system-install

@@ -0,0 +1,45 @@
+#!/bin/sh
+
+# install the gitolite software *system wide*.  Not too robust, fancy, etc.,
+# but does have a usage message and catches simple problems.
+
+usage() { echo "
+    Usage:
+        $0 shared-bin-dir shared-conf-dir shared-hooks-dir
+
+    Example:
+        $0 /usr/local/bin /var/gitolite/conf /var/gitolite/hooks
+
+    In this example, all the binaries go to /usr/local/bin, and the shared
+    conf and hooks files/directories go to the other 2 directories given
+"
+    exit 1;
+}
+
+die() { echo "$@"; echo; usage; exit 1; }
+
+[ -z "$3" ] && usage
+
+gl_bin_dir=$1
+[ -d $gl_bin_dir ] || die "$gl_bin_dir not found"
+gl_conf_dir=$2
+[ -d $gl_conf_dir ] || die "$gl_conf_dir not found"
+gl_hooks_dir=$3
+[ -d $gl_hooks_dir ] || die "$gl_hooks_dir not found"
+
+bindir=`echo $0 | perl -lpe 's/^/$ENV{PWD}\// unless /^\//; s/\/[^\/]+$//;'`
+cd $bindir/..       # we assume the standard gitolite source tree is here!
+
+cp src/* $gl_bin_dir || die "cp src/* to $gl_bin_dir failed"
+rm $gl_bin_dir/gl-easy-install
+perl -lpi -e "s(^GL_PACKAGE_CONF=.*)(GL_PACKAGE_CONF=$gl_conf_dir)" $gl_bin_dir/gl-setup
+
+cp -R conf/* $gl_conf_dir || die "cp conf/* to $gl_conf_dir failed"
+perl -lpi \
+    -e "s(^#\s*\\\$GL_PACKAGE_CONF\s*=.*)(\\\$GL_PACKAGE_CONF = '$gl_conf_dir';)" \
+        $gl_conf_dir/example.gitolite.rc
+perl -lpi \
+    -e "s(^#\s*\\\$GL_PACKAGE_HOOKS\s*=.*)(\\\$GL_PACKAGE_HOOKS = '$gl_hooks_dir';)" \
+        $gl_conf_dir/example.gitolite.rc
+
+cp -R hooks/* $gl_hooks_dir || die "cp hooks/* to $gl_hooks_dir failed"