From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitweb on shared hosting
Date: Sun, 03 Jun 2007 20:36:01 +0200 [thread overview]
Message-ID: <f3v1cg$ft4$1@sea.gmane.org> (raw)
In-Reply-To: 200706021953.09942.dev.list@mircea.bardac.net
Mircea Bardac wrote:
> It is also very strange to have README/"How to configure gitweb for your local
> system" saying "You can specify the following configuration variables when
> buiding GIT". That means I have to rebuild GIT (actually, only
> gitweb/gitweb.cgi) to configure gitweb => I need to download the sources by
> hand instead of using the already installed gitweb on my system (the one
> which came with the git package).
First, it is when building gitweb/gitweb.cgi from gitweb/gitweb.perl, but
in practice that is just filling configuration in a few places. See the
places in the source, and later you can edit gitweb.cgi by hand.
> Is there any strong reason to have configuration at build-time at all? It
> would be a lot easier IMO to have it *just* by config files. I'm saying this
> because most of the install process is manual anyway (copying/moving files).
You can override configuration using config file (with exception of name of
config file), and put [almost] all configuration in config file.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-06-03 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 16:53 gitweb on shared hosting Mircea Bardac
2007-06-03 18:36 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-03 15:35 Martin Koegler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f3v1cg$ft4$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).