git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Christian Couder <chriscool@tuxfamily.org>,
	Petr Baudis <pasky@suse.cz>,
	Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
	John Hawley <warthog9@kernel.org>
Subject: [RFC] Splitting gitweb and build-time configuration variables
Date: Tue, 17 Aug 2010 20:15:36 +0200	[thread overview]
Message-ID: <201008172015.37353.jnareb@gmail.com> (raw)

I am planning on picking up and resubmitting "splitting gitweb" series,
which was created by Pavan as a prerequisite for adding write and admin
support to gitweb ("Splitting gitweb and developing write 
functionalities (Integrated web client for git)" GSoC 2010 project).

There is a question what to do about gitweb configuration variables 
which are set during build time, like e.g.:

  # URI of stylesheets
  our @stylesheets = ("++GITWEB_CSS++");

or

  # core git executable to use
  # this can just be "git" if your webserver has a sensible PATH
  our $GIT = "++GIT_BINDIR++/git";


I think it was agreed that _setting_ these variables would be left in 
gitweb.perl, to have one single place which gathers all such variables, 
and to have gitweb/Makefile to munge (transform) only a single file.

So those variables would be _declared_ in appropriate gitweb module 
(Gitweb::Git aka Gitweb::Command, Gitweb::Config, Gitweb::Util etc.)
but would be _defined_ (set to value) in gitweb.perl.  The final goal is 
to have gitweb.perl consist only of loading modules, build-time 
configuration, and starting gitweb (calling run() or similarly named 
subroutine or method).

The question is where *description* of those build time configuration 
variables should be (see the above examples).  Should it be:

1. Description of build-time configuration variable is in the module
   that defines it, and each block of variables coming from the same
   module would have notice where one can find description of those
   variables, like in original patches by Pavan, e.g.:

     # Only configuration variables with build-time overridable
     # defaults are listed below. The complete set of variables
     # with their descriptions is listed in Gitweb::Config.

or

2. Description of build-time configuration variables is in gitweb.perl,
   and in each module there is comment that full description of those
   variables can be found there, e.g. (proposal):

     # Values of those variables are set during build time in 
     # gitweb/gitweb.perl (main script).  You can find their description
     # there.

or perhaps

3. Duplicate description of those variables, to have it both in
   appropriate module and in gitweb.perl


What do you think about it?

-- 
Jakub Narebski
Poland

             reply	other threads:[~2010-08-17 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 18:15 Jakub Narebski [this message]
2010-08-18  3:03 ` [RFC] Splitting gitweb and build-time configuration variables Jonathan Nieder
2010-08-18  8:05   ` Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008172015.37353.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=pavan.sss1991@gmail.com \
    --cc=warthog9@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).