On Sun, 12 Sep 2010, Junio C Hamano wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: > > > It is an RFC because I am not sure where to put documentation, > > i.e. description of GITWEB_TEST_INSTALLED. Should it be put in > > t/README, in gitweb/README, or in gitweb/INSTALL, or in > > t/gitweb-lib.sh header? > > I think the comment in this file is fine. O.K. > > + # You can set the GITWEB_TEST_INSTALLED environment variable to > > + # the gitwebdir (the directory where gitweb is installed / deployed to) > > + # of an existing gitweb instalation to test that installation. > > + if test -n "$GITWEB_TEST_INSTALLED" ; then > > + SCRIPT_NAME="$GITWEB_TEST_INSTALLED/gitweb.cgi" > > + test -f "$SCRIPT_NAME" || > > + error "Cannot find gitweb.cgi at $GITWEB_TEST_INSTALLED." > > I don't know if GIT_WEB_TEST_INSTALLED=/path/to/some/directory (naming the > directory that houses the script which must be named gitweb.cgi) is easier > to use than GIT_WEB_TEST_INSTALLED=/path/to/some/gitweb.perl (naming the > script that is allowed to be renamed). First, I was following what GIT_TEST_INSTALLED does (it points to bindir, not to git binary). Second, I had half of idea to also change paths to static files... but they are not used anyway, at least not currently (no check for links). Anyway we can support both situations, slightly similarly to how GIT_TRACE can have different kinds of values. -- Jakub Narebski Poland -- To unsubscribe from this list: 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