Annotation of cvsweb/INSTALL, Revision 4.6
4.6 ! schwarze 1: $Id: INSTALL,v 4.5 2019/11/11 14:37:54 schwarze Exp $
4.2 schwarze 2: $knu: INSTALL,v 1.36 2005/01/22 12:43:55 scop
3.2 knu 3:
4.4 schwarze 4: For notes on upgrading between CVSweb releases, see the bottom
3.29 scop 5: of this document.
3.17 scop 6:
3.16 scop 7: 1) To get cvsweb.cgi to work, make sure that you have Perl 5.6.0 or
3.7 scop 8: newer installed and a web server which is capable of executing CGI
3.18 scop 9: scripts. See also samples/cvsweb-httpd.conf.
3.7 scop 10:
3.10 scop 11: CVSweb uses the following Perl modules. Chances are that some of
3.7 scop 12: these are already installed with your Perl distribution. The oldest
13: Perl distributions, if any, that already ship with these modules have
14: been marked below. If your Perl doesn't have some of the modules,
15: you can get them from CPAN, <http://www.cpan.org/>. Be sure to
16: install also the prerequisites these modules may have. Note that
17: this list contains only modules that aren't already part of Perl
3.16 scop 18: 5.6.0 and newer.
3.17 scop 19:
3.7 scop 20:
3.11 scop 21: Module Version Ships with Perl Type
22: ----------------------------------------------------------
23: File::Temp 5.8.0 required
3.12 scop 24: IPC::Run N/A required
3.11 scop 25: MIME::Types N/A optional
3.15 scop 26: URI N/A required
3.1 knu 27:
3.4 scop 28: Surprisingly enough, you need to have cvs installed. The recommended
29: version of cvs is 1.11 or newer. Older cvs versions may work with
30: more or less quirks, YMMV.
31:
32: Currently, you'll also need to have the GNU RCS utilities 'rlog',
3.17 scop 33: 'rcsdiff' installed (current version is 5.7).
3.1 knu 34:
3.6 scop 35: This may change if cvs will be able to serve these functions without
36: having a working directory [see TODO].
3.1 knu 37:
3.6 scop 38: Note that the cvsweb.cgi script needs to have physical access to the
39: repository (or a copy of it) therefore; rsh, ssh or pserver access
40: doesn't work yet.
41:
3.29 scop 42: Install CVSHistory if you want to use it with CVSweb, and see (8) for
43: configuration notes. You'll need version 2.0 or newer.
44:
3.17 scop 45: 2) Copy cvsweb.conf to a configuration directory, typically
46: /usr/local/etc/cvsweb/cvsweb.conf.
47: Edit cvsweb.conf to fit your needs, you'll probably need to tweak the
48: CVS root(s) of the Repository(ies) you want to view.
3.26 scop 49: See also the @command_path variable for the path where cvsweb.cgi
3.17 scop 50: looks for the various external executables it interacts with.
3.26 scop 51: The other cvsweb.conf-* files are example per-cvsroot configuration files,
52: see commentary in cvsweb.conf for more information.
3.17 scop 53:
54: 3) Copy cvsweb.cgi to a directory of your web server where the execution
55: of CGI scripts is allowed. Edit it to make the variable $config
56: (look for 'Configuration Area') point to your configuration file.
3.4 scop 57: If your perl binary isn't located in /usr/bin you'll have to edit the
3.26 scop 58: first line of the script as well. For Apache web servers, there is an
59: optional sample httpd.conf snippet in the samples/ directory. Most
60: setups do not need it though, it is only for advanced and/or mod_perl
61: configurations.
3.1 knu 62:
3.4 scop 63: 4) If you do not have the dir.gif, text.gif and back.gif icons, copy
64: them somewhere in your $DocumentRoot and edit the %ICONS hash
65: in cvsweb.conf. You won't need to do this if you have a stock
66: Apache installed - they're located in the default icons directory.
3.1 knu 67: The icons distributed with this cvsweb are in the public domain.
3.4 scop 68: If you think that the default icons are too large, use the corresponding
69: mini icons in the icons/ directory and change the %ICONS hash in
3.1 knu 70: cvsweb.conf.
71:
3.6 scop 72: 5) Copy cvsweb.css from the css/ directory to a web server directory, and
73: point the $cssurl variable in cvsweb.conf to it.
74:
3.29 scop 75: 8) CVSHistory <http://www.jamwt.com/CVSHistory/> can be used with this
76: version of CVSweb. See the $cvshistory_url configuration variable in
77: cvsweb.conf. For best results, configure CVSweb and CVSHistory to use
78: the same "logical names" for CVS roots.
3.1 knu 79:
3.17 scop 80: 9) If you like you can add descriptions to be shown next to each directory
3.4 scop 81: or module name. These are read from CVSROOT/descriptions.
3.1 knu 82:
83: - Check out a copy of your CVSROOT
84: - edit checkoutlist and add a line that says
85: descriptions
3.17 scop 86: - Edit descriptions. Add one line for each directory that you would like
3.1 knu 87: to have a comment for. You can have HTML in the descriptions.
88: These lines are relative from the $CVSROOT. Example:
3.22 scop 89: JVote An application to assist with <a href="http://www.irtc.org/">IRTC</a> voting
3.3 knu 90: JVote/images Store the images for JVote
91: JVote/tools Scripts to startup JVote
3.1 knu 92: - cvs add descriptions
93: - cvs commit
94: - Set $use_descriptions to 1 in cvsweb.conf.
95:
3.29 scop 96: 10) Have fun!
3.1 knu 97:
3.17 scop 98: Troubleshooting
99: ---------------
3.1 knu 100:
101: If you've trouble to make cvsweb.cgi work ...
102: .. if nothing seems to work:
3.17 scop 103: o Check if you can execute CGI scripts (Apache needs to have an
104: ScriptAlias /cgi-bin or cgi-script Handler defined). Try to
3.4 scop 105: execute a simple CGI script that often comes with the distribution
106: of the web server; locate the log files and try to find hints
107: which explain the malfunction.
3.32 scop 108: o View the entries in the web server's error.log. Set $DEBUG to 1 in
109: cvsweb.conf to get more error output.
3.1 knu 110:
111: .. If cvsweb seems to work but doesn't show the expected result
112: (Typical error: you can't see any files)
3.4 scop 113: o Check whether the CGI script has read permissions to your
3.17 scop 114: CVS repository. The CGI script often runs as the user 'nobody'
115: or 'httpd'.
116: o If you use annotation, see @annotate_options in cvsweb.conf.
117: o See CVSROOT/config for various options controlling what gets written
118: into CVSROOT/history, where lock files are placed etc. You can also
119: build a fake cvsroot with symlinks to the 'real' CVS directories and make
3.1 knu 120: a fake CVSROOT/history as symbolic link to /dev/null.
3.17 scop 121: If you don't want cvs called from cvsweb to place read locks at all, let
3.1 knu 122: cvsweb operate on a copy.
3.17 scop 123: o Does cvsweb find your RCS utils/cvs binary(annotate)?
124: See $command_path in in cvsweb.conf.
125: o cvsweb allows for compression now. It is determined first if the
126: browser accepts gzip encoding. But - no rule without exception - some
127: versions of MSIE claim to understand gzip encoded content but
128: display garbage .. so compression for MSIE is disabled now. Maybe you
129: find another browser with this problem, then you should disable
4.1 schwarze 130: compression ($allow_compress=0 in cvsweb.conf).
3.17 scop 131:
3.31 scop 132: Upgrade instructions
133: --------------------
134:
4.4 schwarze 135: List of things to pay attention to when upgrading CVSweb from
3.34 scop 136: earlier versions follows. Lack of instructions for a particular
137: version means that there are no special things to pay attention to.
3.31 scop 138:
3.36 scop 139: Upgrading to 3.0.5
3.35 scop 140: ------------------
141:
142: The following configuration variables in cvsweb.conf have changed:
143:
144: $allow_mailtos is new, and optional. See comments in cvsweb.conf.
145:
3.34 scop 146: Upgrading to 3.0.3
147: ------------------
148:
149: The following configuration variables in cvsweb.conf have changed:
150:
151: $DEBUG is new, and optional. See comments in cvsweb.conf.
152:
153: Upgrading to 3.0.1
154: ------------------
3.29 scop 155:
156: The following configuration variables in cvsweb.conf have changed:
157:
158: $cvshistory_url is new, and optional. See comments in cvsweb.conf.
3.17 scop 159:
3.34 scop 160: Upgrading to 3.0.0
161: ------------------
3.17 scop 162:
163: Make sure that the dependencies are met, see 1) above.
164:
165: The following configuration variables in cvsweb.conf have changed:
166:
3.24 scop 167: $command_path has been changed to @command_path, ie. a list.
168:
3.25 scop 169: @HideModules has been removed. It had nothing to do with actual
170: modules in CVS terminology, and the implementation was broken.
171: @ForbiddenFiles has been enhanced to affect directories as well.
172:
3.17 scop 173: $cvstreedefault is now optional. If unset, the first one in
174: @CVSrepositories is used.
175:
176: %DEFAULTVALUE for "ln" can now be set to a boolean indicating whether
177: line numbers in markup views should be shown or not. The default is off.
178:
3.20 scop 179: The following parameters have been removed, use CSS instead:
3.17 scop 180: $body_tag, $body_tag_for_src, $navigationHeaderColor, $dirtable,
181: @tabcolors, $columnHeaderColorDefault, $columnHeaderColorSorted,
182: $tableBorderColor, $diffcolorHeading, $diffcolorEmpty, $diffcolorRemove,
183: $diffcolorChange, $diffcolorAdd, $diffcolorDarkChange, $difffontface,
184: $difffontsize, $markupLogColor.
3.20 scop 185:
186: The following parameters have been removed, with no replacement:
3.21 scop 187: $open_extern_window, $extern_window_height, $extern_window_width,
188: $checkout_magic.
3.17 scop 189:
190: $file_list_len can be set to work around problems with rlog(1) and dirs
191: with lots of files.
192:
193: $cssurl contains the absolute URI to the CSS file to use.
194:
4.5 schwarze 195: %ICONS has a new entry: binfile for binary files (-kb keyword
196: substitution).
3.23 scop 197:
198: %DIFF_COMMANDS is new, it is used to configure external per file type
199: diff commands.
CVSweb