From: gerv%gerv.net <>
Date: Sun, 12 May 2002 20:16:48 +0000 (+0000)
Subject: Initial checkin of a couple of new files I split out.
X-Git-Tag: bugzilla-2.16rc2~46
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=327e8399319b319ce4aed46201a1e746478d5b82;p=thirdparty%2Fbugzilla.git
Initial checkin of a couple of new files I split out.
---
diff --git a/docs/sgml/gd-makefile.patch b/docs/sgml/gd-makefile.patch
new file mode 100644
index 0000000000..8ec35a23a5
--- /dev/null
+++ b/docs/sgml/gd-makefile.patch
@@ -0,0 +1,22 @@
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
+
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
+
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
+
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
+
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
diff --git a/docs/sgml/glossary.sgml b/docs/sgml/glossary.sgml
index 3e40df58ac..1dda72d3cb 100644
--- a/docs/sgml/glossary.sgml
+++ b/docs/sgml/glossary.sgml
@@ -15,10 +15,7 @@
to keep secret files which would otherwise
compromise your installation - e.g. the
localconfig
-
- file contains the password to your database. If this information were
- generally available, and remote access to your database turned on,
- you risk corruption of your database by computer criminals or the
+ file contains the password to your database.
curious.
@@ -56,7 +53,7 @@
A
- Bug
+ bug
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
@@ -71,33 +68,18 @@
Bug Number
- Each Bugzilla Bug is assigned a number that uniquely identifies
- that Bug. The Bug associated with a Bug Number can be pulled up via a
+ Each Bugzilla bug is assigned a number that uniquely identifies
+ that bug. The bug associated with a bug number can be pulled up via a
query, or easily from the very front page by typing the number in the
"Find" box.
-
- Bug Life Cycle
-
-
- A Bug has stages through which it must pass before becoming a
- closed bug
,
- including acceptance, resolution, and verification. The
- Bug Life Cycle
-
- is moderately flexible according to the needs of the organization
- using it, though.
-
-
-
Bugzilla
- Bugzilla is the industry-standard bug tracking system. It is
- quite popular among Open Source enthusiasts.
+ Bugzilla is the world-leading free software bug tracking system.
@@ -127,14 +109,11 @@
CPAN
stands for the
- Comprehensive Perl Archive Network
-
- . CPAN maintains a large number of extremely useful
+ Comprehensive Perl Archive Network
.
+ CPAN maintains a large number of extremely useful
Perl
-
- modules. By themselves, Perl modules generally do nothing, but when
- used as part of a larger program, they provide much-needed algorithms
- and functionality.
+ modules - encapsulated chunks of code for performing a
+ particular task.
@@ -169,33 +148,16 @@
Groups
has a very special meaning to Bugzilla. Bugzilla's main security
- mechanism comes by lumping users into groups, and assigning those
- groups certain privileges to
+ mechanism comes by placing users in groups, and assigning those
+ groups certain privileges to view bugs in particular
Products
-
- and
- Components
-
in the
Bugzilla
-
database.
-
- I
-
-
- Infinite Loop
-
-
- A loop of information that never ends; see recursion.
-
-
-
-
M
@@ -221,10 +183,11 @@
Product
- A Product is a broad category of types of bugs. In general,
- there are several Components to a Product. A Product may also define a
+ A Product is a broad category of types of bugs, normally
+ representing a single piece of software or entity. In general,
+ there are several Components to a Product. A Product may define a
group (used for security) for all bugs entered into
- components beneath it.
+ its Components.
@@ -262,24 +225,7 @@
bugs over their life cycle, thus the need for the
QA Contact
- field in a Bug.
-
-
-
-
-
- R
-
-
- Recursion
-
-
- The property of a function looking back at itself for
- something.
- GNU
, for instance, stands for
- GNU's Not UNIX
,
- thus recursing upon itself for definition. For further clarity, see
- Infinite Loop.
+ field in a bug.
diff --git a/docs/sgml/introduction.sgml b/docs/sgml/introduction.sgml
new file mode 100644
index 0000000000..88f9b26822
--- /dev/null
+++ b/docs/sgml/introduction.sgml
@@ -0,0 +1,146 @@
+
+ Introduction
+
+
+ What is Bugzilla?
+
+
+ Bugzilla is a bug- or issue-tracking system. Bug-tracking
+ systems allow individual or groups of developers effectively to keep track
+ of outstanding problems with their product.
+ Bugzilla was originally
+ written by Terry Weissman in a programming language called TCL, to
+ replace a rudimentary bug-tracking database used internally by Netscape
+ Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
+ it remains to this day. Most commercial defect-tracking software vendors
+ at the time charged enormous licensing fees, and Bugzilla quickly became
+ a favorite of the open-source crowd (with its genesis in the open-source
+ browser project, Mozilla). It is now the de-facto standard
+ defect-tracking system against which all others are measured.
+
+
+ Bugzilla boasts many advanced features. These include:
+
+
+ Powerful searching
+
+
+
+ User-configurable email notifications of bug changes
+
+
+
+ Full change history
+
+
+
+ Inter-bug dependency tracking and graphing
+
+
+
+ Excellent attachment management
+
+
+
+ Integrated, product-based, granular security schema
+
+
+
+ Fully security-audited, and runs under Perl's taint mode
+
+
+
+ A robust, stable RDBMS back-end
+
+
+
+ Web, XML, email and console interfaces
+
+
+
+ Completely customisable and/or localisable web user
+ interface
+
+
+
+ Extensive configurability
+
+
+
+ Smooth upgrade pathway between versions
+
+
+
+
+
+
+ Why Should We Use Bugzilla?
+
+ For many years, defect-tracking software has remained principally
+ the domain of large software development houses. Even then, most shops
+ never bothered with bug-tracking software, and instead simply relied on
+ shared lists and email to monitor the status of defects. This procedure
+ is error-prone and tends to cause those bugs judged least significant by
+ developers to be dropped or ignored.
+
+ These days, many companies are finding that integrated
+ defect-tracking systems reduce downtime, increase productivity, and raise
+ customer satisfaction with their systems. Along with full disclosure, an
+ open bug-tracker allows manufacturers to keep in touch with their clients
+ and resellers, to communicate about problems effectively throughout the
+ data management chain. Many corporations have also discovered that
+ defect-tracking helps reduce costs by providing IT support
+ accountability, telephone support knowledge bases, and a common,
+ well-understood system for accounting for unusual system or software
+ issues.
+
+ But why should
+ you
+
+ use Bugzilla?
+
+ Bugzilla is very adaptable to various situations. Known uses
+ currently include IT support queues, Systems Administration deployment
+ management, chip design and development problem tracking (both
+ pre-and-post fabrication), and software and hardware bug tracking for
+ luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
+ Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
+ provides a powerful, easy-to-use solution to configuration management and
+ replication problems.
+
+ Bugzilla can dramatically increase the productivity and
+ accountability of individual employees by providing a documented workflow
+ and positive feedback for good performance. How many times do you wake up
+ in the morning, remembering that you were supposed to do
+ something
+ today, but you just can't quite remember? Put it in Bugzilla, and you
+ have a record of it from which you can extrapolate milestones, predict
+ product versions for integration, and follow the discussion trail
+ that led to critical decisions.
+
+ Ultimately, Bugzilla puts the power in your hands to improve your
+ value to your employer or business while providing a usable framework for
+ your natural attention to detail and knowledge store to flourish.
+
+
+
+
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml
index 540109febc..9deb43bd68 100644
--- a/docs/sgml/patches.sgml
+++ b/docs/sgml/patches.sgml
@@ -26,83 +26,42 @@
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
+
+ Command-line Bugzilla Queries
- 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!
+ There are a suite of utilities for querying Bugzilla from the
+ command line. Although there's no particular reason why they
+ shouldn't work, they have not been tested with 2.16.
- 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.
+ Download three files:
- bash#
+ bash$
- chmod u+w *
+ wget -O query.conf
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'
@@ -110,9 +69,10 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
- bash#
+ bash$
- chmod u+x duplicates.cgi
+ wget -O buglist
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'
@@ -122,7 +82,8 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
bash#
- chmod a-x bug_status.html
+ wget -O bugs
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'
@@ -130,41 +91,20 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
- Run the script:
-
-
-
- bash#
-
- ./setperl.csh /your/path/to/perl
-
-
-
- Using Setperl to set your perl path
-
-
-
- bash#
+ Make your utilities executable:
+
+ bash$
- ./setperl.csh /usr/bin/perl
-
-
-
+ chmod u+x buglist bugs
+
-
-
-
- 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
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
the resulting HTML page to stdout. It supports both short options, (such
@@ -191,71 +131,26 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
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",
+ Quicksearch is a single-text-box query tool which uses metacharacters
+ to indicate what is to be searched. For example, "foo@bar.com" would be
+ looked for in email address fields, because it contains an @ and so
+ is an email address.
+
+
+ Quicksearch consists 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.
+ "quicksearchhack.html". More information on how to use Quicksearch
+ can be found there. You'll find the Quicksearch box on Bugzilla's
+ front page.
To take full advantage of the query power, the Bugzilla maintainer
- must edit "localconfig.js" according to the value sets used in the local
+ must edit "localconfig.js" and change the parameters according to the local
installation.
Currently, keywords must be hard-coded in localconfig.js. If they
diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml
index 0626902720..b2dc6faf64 100644
--- a/docs/sgml/variants.sgml
+++ b/docs/sgml/variants.sgml
@@ -13,13 +13,13 @@
Red Hat Bugzilla
- Red Hat Bugzilla is probably the most popular Bugzilla variant on
- the planet. One of the major benefits of Red Hat Bugzilla is the ability
+ Red Hat Bugzilla is probably the most popular Bugzilla, after
+ Bugzilla itself, on the planet. One of the major benefits of Red Hat
+ Bugzilla is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
- back-end, instead of just MySQL. Dave Lawrence has worked very hard to
- keep Red Hat Bugzilla up-to-date, and many people prefer the
- snappier-looking page layout of Red Hat Bugzilla to the default
- Mozilla-standard formatting.
+ back-end, instead of just MySQL. Dave Lawrence of Red Hat is
+ active in the Bugzilla community, and we hope to see a reunification
+ of the fork before too long.
URL:
@@ -48,7 +48,7 @@
Scarab
- Scarab is a new bug-tracking system built using Java
+ Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 7.
URL:
diff --git a/docs/xml/gd-makefile.patch b/docs/xml/gd-makefile.patch
new file mode 100644
index 0000000000..8ec35a23a5
--- /dev/null
+++ b/docs/xml/gd-makefile.patch
@@ -0,0 +1,22 @@
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
+
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
+
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
+
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
+
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
diff --git a/docs/xml/glossary.xml b/docs/xml/glossary.xml
index 3e40df58ac..1dda72d3cb 100644
--- a/docs/xml/glossary.xml
+++ b/docs/xml/glossary.xml
@@ -15,10 +15,7 @@
to keep secret files which would otherwise
compromise your installation - e.g. the
localconfig
-
- file contains the password to your database. If this information were
- generally available, and remote access to your database turned on,
- you risk corruption of your database by computer criminals or the
+ file contains the password to your database.
curious.
@@ -56,7 +53,7 @@
A
- Bug
+ bug
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
@@ -71,33 +68,18 @@
Bug Number
- Each Bugzilla Bug is assigned a number that uniquely identifies
- that Bug. The Bug associated with a Bug Number can be pulled up via a
+ Each Bugzilla bug is assigned a number that uniquely identifies
+ that bug. The bug associated with a bug number can be pulled up via a
query, or easily from the very front page by typing the number in the
"Find" box.
-
- Bug Life Cycle
-
-
- A Bug has stages through which it must pass before becoming a
- closed bug
,
- including acceptance, resolution, and verification. The
- Bug Life Cycle
-
- is moderately flexible according to the needs of the organization
- using it, though.
-
-
-
Bugzilla
- Bugzilla is the industry-standard bug tracking system. It is
- quite popular among Open Source enthusiasts.
+ Bugzilla is the world-leading free software bug tracking system.
@@ -127,14 +109,11 @@
CPAN
stands for the
- Comprehensive Perl Archive Network
-
- . CPAN maintains a large number of extremely useful
+ Comprehensive Perl Archive Network
.
+ CPAN maintains a large number of extremely useful
Perl
-
- modules. By themselves, Perl modules generally do nothing, but when
- used as part of a larger program, they provide much-needed algorithms
- and functionality.
+ modules - encapsulated chunks of code for performing a
+ particular task.
@@ -169,33 +148,16 @@
Groups
has a very special meaning to Bugzilla. Bugzilla's main security
- mechanism comes by lumping users into groups, and assigning those
- groups certain privileges to
+ mechanism comes by placing users in groups, and assigning those
+ groups certain privileges to view bugs in particular
Products
-
- and
- Components
-
in the
Bugzilla
-
database.
-
- I
-
-
- Infinite Loop
-
-
- A loop of information that never ends; see recursion.
-
-
-
-
M
@@ -221,10 +183,11 @@
Product
- A Product is a broad category of types of bugs. In general,
- there are several Components to a Product. A Product may also define a
+ A Product is a broad category of types of bugs, normally
+ representing a single piece of software or entity. In general,
+ there are several Components to a Product. A Product may define a
group (used for security) for all bugs entered into
- components beneath it.
+ its Components.
@@ -262,24 +225,7 @@
bugs over their life cycle, thus the need for the
QA Contact
- field in a Bug.
-
-
-
-
-
- R
-
-
- Recursion
-
-
- The property of a function looking back at itself for
- something.
- GNU
, for instance, stands for
- GNU's Not UNIX
,
- thus recursing upon itself for definition. For further clarity, see
- Infinite Loop.
+ field in a bug.
diff --git a/docs/xml/introduction.xml b/docs/xml/introduction.xml
new file mode 100644
index 0000000000..88f9b26822
--- /dev/null
+++ b/docs/xml/introduction.xml
@@ -0,0 +1,146 @@
+
+ Introduction
+
+
+ What is Bugzilla?
+
+
+ Bugzilla is a bug- or issue-tracking system. Bug-tracking
+ systems allow individual or groups of developers effectively to keep track
+ of outstanding problems with their product.
+ Bugzilla was originally
+ written by Terry Weissman in a programming language called TCL, to
+ replace a rudimentary bug-tracking database used internally by Netscape
+ Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
+ it remains to this day. Most commercial defect-tracking software vendors
+ at the time charged enormous licensing fees, and Bugzilla quickly became
+ a favorite of the open-source crowd (with its genesis in the open-source
+ browser project, Mozilla). It is now the de-facto standard
+ defect-tracking system against which all others are measured.
+
+
+ Bugzilla boasts many advanced features. These include:
+
+
+ Powerful searching
+
+
+
+ User-configurable email notifications of bug changes
+
+
+
+ Full change history
+
+
+
+ Inter-bug dependency tracking and graphing
+
+
+
+ Excellent attachment management
+
+
+
+ Integrated, product-based, granular security schema
+
+
+
+ Fully security-audited, and runs under Perl's taint mode
+
+
+
+ A robust, stable RDBMS back-end
+
+
+
+ Web, XML, email and console interfaces
+
+
+
+ Completely customisable and/or localisable web user
+ interface
+
+
+
+ Extensive configurability
+
+
+
+ Smooth upgrade pathway between versions
+
+
+
+
+
+
+ Why Should We Use Bugzilla?
+
+ For many years, defect-tracking software has remained principally
+ the domain of large software development houses. Even then, most shops
+ never bothered with bug-tracking software, and instead simply relied on
+ shared lists and email to monitor the status of defects. This procedure
+ is error-prone and tends to cause those bugs judged least significant by
+ developers to be dropped or ignored.
+
+ These days, many companies are finding that integrated
+ defect-tracking systems reduce downtime, increase productivity, and raise
+ customer satisfaction with their systems. Along with full disclosure, an
+ open bug-tracker allows manufacturers to keep in touch with their clients
+ and resellers, to communicate about problems effectively throughout the
+ data management chain. Many corporations have also discovered that
+ defect-tracking helps reduce costs by providing IT support
+ accountability, telephone support knowledge bases, and a common,
+ well-understood system for accounting for unusual system or software
+ issues.
+
+ But why should
+ you
+
+ use Bugzilla?
+
+ Bugzilla is very adaptable to various situations. Known uses
+ currently include IT support queues, Systems Administration deployment
+ management, chip design and development problem tracking (both
+ pre-and-post fabrication), and software and hardware bug tracking for
+ luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
+ Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
+ provides a powerful, easy-to-use solution to configuration management and
+ replication problems.
+
+ Bugzilla can dramatically increase the productivity and
+ accountability of individual employees by providing a documented workflow
+ and positive feedback for good performance. How many times do you wake up
+ in the morning, remembering that you were supposed to do
+ something
+ today, but you just can't quite remember? Put it in Bugzilla, and you
+ have a record of it from which you can extrapolate milestones, predict
+ product versions for integration, and follow the discussion trail
+ that led to critical decisions.
+
+ Ultimately, Bugzilla puts the power in your hands to improve your
+ value to your employer or business while providing a usable framework for
+ your natural attention to detail and knowledge store to flourish.
+
+
+
+
diff --git a/docs/xml/patches.xml b/docs/xml/patches.xml
index 540109febc..9deb43bd68 100644
--- a/docs/xml/patches.xml
+++ b/docs/xml/patches.xml
@@ -26,83 +26,42 @@
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
+
+ Command-line Bugzilla Queries
- 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!
+ There are a suite of utilities for querying Bugzilla from the
+ command line. Although there's no particular reason why they
+ shouldn't work, they have not been tested with 2.16.
- 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.
+ Download three files:
- bash#
+ bash$
- chmod u+w *
+ wget -O query.conf
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'
@@ -110,9 +69,10 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
- bash#
+ bash$
- chmod u+x duplicates.cgi
+ wget -O buglist
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'
@@ -122,7 +82,8 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
bash#
- chmod a-x bug_status.html
+ wget -O bugs
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'
@@ -130,41 +91,20 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
- Run the script:
-
-
-
- bash#
-
- ./setperl.csh /your/path/to/perl
-
-
-
- Using Setperl to set your perl path
-
-
-
- bash#
+ Make your utilities executable:
+
+ bash$
- ./setperl.csh /usr/bin/perl
-
-
-
+ chmod u+x buglist bugs
+
-
-
-
- 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
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
the resulting HTML page to stdout. It supports both short options, (such
@@ -191,71 +131,26 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
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",
+ Quicksearch is a single-text-box query tool which uses metacharacters
+ to indicate what is to be searched. For example, "foo@bar.com" would be
+ looked for in email address fields, because it contains an @ and so
+ is an email address.
+
+
+ Quicksearch consists 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.
+ "quicksearchhack.html". More information on how to use Quicksearch
+ can be found there. You'll find the Quicksearch box on Bugzilla's
+ front page.
To take full advantage of the query power, the Bugzilla maintainer
- must edit "localconfig.js" according to the value sets used in the local
+ must edit "localconfig.js" and change the parameters according to the local
installation.
Currently, keywords must be hard-coded in localconfig.js. If they
diff --git a/docs/xml/variants.xml b/docs/xml/variants.xml
index 0626902720..b2dc6faf64 100644
--- a/docs/xml/variants.xml
+++ b/docs/xml/variants.xml
@@ -13,13 +13,13 @@
Red Hat Bugzilla
- Red Hat Bugzilla is probably the most popular Bugzilla variant on
- the planet. One of the major benefits of Red Hat Bugzilla is the ability
+ Red Hat Bugzilla is probably the most popular Bugzilla, after
+ Bugzilla itself, on the planet. One of the major benefits of Red Hat
+ Bugzilla is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
- back-end, instead of just MySQL. Dave Lawrence has worked very hard to
- keep Red Hat Bugzilla up-to-date, and many people prefer the
- snappier-looking page layout of Red Hat Bugzilla to the default
- Mozilla-standard formatting.
+ back-end, instead of just MySQL. Dave Lawrence of Red Hat is
+ active in the Bugzilla community, and we hope to see a reunification
+ of the fork before too long.
URL:
@@ -48,7 +48,7 @@
Scarab
- Scarab is a new bug-tracking system built using Java
+ Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 7.
URL: