From d8caf6045d10344c431918128e3803ca497565f3 Mon Sep 17 00:00:00 2001
From: "gerv%gerv.net" <>
Date: Sun, 28 Jul 2002 05:00:17 +0000
Subject: Merging new docs from 2.16 branch.
---
docs/sgml/patches.sgml | 241 +++++--------------------------------------------
1 file changed, 24 insertions(+), 217 deletions(-)
(limited to 'docs/sgml/patches.sgml')
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml
index 540109feb..43f816758 100644
--- a/docs/sgml/patches.sgml
+++ b/docs/sgml/patches.sgml
@@ -26,160 +26,54 @@
setting up your VirtualHost section for Bugzilla with a rule like
this:
-
-
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-]]>
-
+]]>
There are many, many more things you can do with mod_rewrite.
- As time goes on, I will include many more in the Guide. For now,
- though, please refer to the mod_rewrite documentation at
- http://www.apache.org
+ Please refer to the mod_rewrite documentation at
+ http://www.apache.org.
-
- The setperl.csh Utility
-
- You can use the "setperl.csh" utility to quickly and easily change
- the path to perl on all your Bugzilla files. This is a C-shell script; if
- you do not have "csh" or "tcsh" in the search path on your system, it
- will not work!
-
-
-
- Download the "setperl.csh" utility to your Bugzilla directory
- and make it executable.
-
-
-
-
-
- bash#
-
- cd /your/path/to/bugzilla
-
-
-
-
-
-
-
- bash#
-
- wget -O setperl.csh
- 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'
-
-
-
-
-
-
-
- bash#
-
- chmod u+x setperl.csh
-
-
-
-
-
-
-
- Prepare (and fix) Bugzilla file permissions.
-
-
-
-
-
- bash#
-
- chmod u+w *
-
-
-
-
-
-
-
- bash#
-
- chmod u+x duplicates.cgi
-
-
-
-
-
-
-
- bash#
-
- chmod a-x bug_status.html
-
-
-
-
-
-
-
- Run the script:
-
-
-
- bash#
-
- ./setperl.csh /your/path/to/perl
-
-
-
- Using Setperl to set your perl path
-
-
-
- bash#
-
- ./setperl.csh /usr/bin/perl
-
-
-
-
-
-
-
-
Command-line Bugzilla Queries
- Users can query Bugzilla from the command line using this suite of
- utilities.
-
- The query.conf file contains the mapping from options to field
+ There are a suite of Unix utilities for querying Bugzilla from the
+ command line. They live in the
+ contrib/cmdline
+ directory. However, they
+ have not yet been updated to work with 2.16 (post-templatisation.).
+ There are three files - query.conf,
+ buglist and bugs.
+
+ query.conf
+ contains the mapping from options to field
names and comparison types. Quoted option names are "grepped" for, so it
should be easy to edit this file. Comments (#) have no effect; you must
- make sure these lines do not contain any quoted "option"
+ make sure these lines do not contain any quoted "option".
- buglist is a shell script which submits a Bugzilla query and writes
+ buglist
+ is a shell script which submits a Bugzilla query and writes
the resulting HTML page to stdout. It supports both short options, (such
as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
"--reporter=bar"). If the first character of an option is not "-", it is
treated as if it were prefixed with "--default=".
- The columlist is taken from the COLUMNLIST environment variable.
+ The column list is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list bugs in
- buglist.cgi. If you have already used Bugzilla, use
- grep COLUMLIST ~/.netscape/cookies
-
- to see your current COLUMNLIST setting.
+ buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
+ in your cookies file to see your current COLUMNLIST setting.
- bugs is a simple shell script which calls buglist and extracts the
+ bugs is a simple shell script which calls
+ buglist and extracts the
bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into
a working link if any bugs are found. Counting bugs is easy. Pipe the
@@ -187,100 +81,13 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
- Akkana says she has good results piping buglist output through
+ Akkana Peck says she has good results piping
+ buglist output through
w3m -T text/html -dump
-
-
- Download three files:
-
-
-
-
-
- bash$
-
- wget -O query.conf
- 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'
-
-
-
-
-
-
-
- bash$
-
- wget -O buglist
- 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'
-
-
-
-
-
-
-
- bash#
-
- wget -O bugs
- 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'
-
-
-
-
-
-
-
- Make your utilities executable:
-
- bash$
-
- chmod u+x buglist bugs
-
-
-
-
-
- The Quicksearch Utility
-
- Quicksearch is a new, experimental feature of the 2.12 release. It
- consist of two Javascript files, "quicksearch.js" and "localconfig.js",
- and two documentation files, "quicksearch.html" and
- "quicksearchhack.html"
-
- The index.html page has been updated to include the QuickSearch
- text box.
-
- To take full advantage of the query power, the Bugzilla maintainer
- must edit "localconfig.js" according to the value sets used in the local
- installation.
-
- Currently, keywords must be hard-coded in localconfig.js. If they
- are not, keywords are not automatically recognized. This means, if
- localconfig.js is left unconfigured, that searching for a bug with the
- "foo" keyword will only find bugs with "foo" in the summary, status
- whiteboard, product or component name, but not those with the keyword
- "foo".
-
- Workarounds for Bugzilla users:
-
- search for '!foo' (this will find only bugs with the keyword
- "foo"
-
- search 'foo,!foo' (equivalent to 'foo OR keyword:foo')
-
-
-
- When this tool is ported from client-side JavaScript to server-side
- Perl, the requirement for hard-coding keywords can be fixed.
- This
- bug
-
- has details.
-