Martin Langhoff wrote: > On 6/18/06, Jakub Narebski <jnareb@xxxxxxxxx> wrote: >> So GIT_CONFIG would be ~/.gitconfig, and GIT_CONFIG_LOCAL would be >> $GIT_DIR/config or what? > > I don't quite follow why gitweb needs a GIT_CONFIG_LOCAL defined. > Given that it works in a CGI environment, it should read > $GIT_DIR/config by default, and $GIT_CONFIG if set (from httpd.conf). When talking about gitweb [installation] configuration, including where to find GIT projects to display, one needs to remember that gitweb might (and probably is) installed from binary package and not git.git, and git/.git/config might not exist. So we have the following options to separate gitweb-wide options: - use ~/.gitconfig, /etc/gitconfig or some other global git configuration file, reading values using '$gitexecdir/git-repo-config'. Problem: bootstraping, namely value of $gitexecdir ($gitbin now) needs to be set in gitweb.cgi, perhaps during the build process. - use gitweb.conf for configuration, reading values via equivalent of 'GIT_CONFIG=gitweb.conf $gitexecdir/git-repo-config'. Problem: bootstraping, namely value of $gitexecdir ($gitbin now) needs to be set in gitweb.cgi, perhaps during the build process. - use gitweb.conf for configuration, following the .git/config format, writing parsing of ini file (reading only) in Perl from scratch (or use one of many CPAN modules). - use Perl for configuration file, a la Jon Loeliger <jdl@xxxxxxx> patch: http://marc.theaimsgroup.com/?l=git&m=114308224922372&w=2 -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html