aboutsummaryrefslogtreecommitdiffstats
path: root/docs/html/os-specific.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2004-01-25 02:30:57 +0000
committergerv%gerv.net <>2004-01-25 02:30:57 +0000
commit6c709dd097e65025038a0dc9c17fad6a88e99b6b (patch)
treec0c33411898e67410829ea142458440fe912b388 /docs/html/os-specific.html
parentc7f3e4a3a055bbbec29a8731f388f9fa4648c768 (diff)
downloadbugs-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar
bugs-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.gz
bugs-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.bz2
bugs-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.xz
bugs-6c709dd097e65025038a0dc9c17fad6a88e99b6b.zip
Massive rearrangement of the installation section. Hopefully it makes sense now.
Diffstat (limited to 'docs/html/os-specific.html')
-rw-r--r--docs/html/os-specific.html125
1 files changed, 47 insertions, 78 deletions
diff --git a/docs/html/os-specific.html b/docs/html/os-specific.html
index 98aa8e3a6..224651cf2 100644
--- a/docs/html/os-specific.html
+++ b/docs/html/os-specific.html
@@ -1,24 +1,24 @@
<HTML
><HEAD
><TITLE
->OS Specific Installation Notes</TITLE
+>OS-Specific Installation Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5
+TITLE="The Bugzilla Guide - 2.17.7
Development Release"
HREF="index.html"><LINK
REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
REL="PREVIOUS"
TITLE="Optional Additional Configuration"
HREF="extraconfig.html"><LINK
REL="NEXT"
-TITLE="Bugzilla Security"
-HREF="security.html"></HEAD
+TITLE="Troubleshooting"
+HREF="troubleshooting.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide - 2.17.5
+>The Bugzilla Guide - 2.17.7
Development Release</TH
></TR
><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Installation</TD
+>Chapter 2. Installing Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="security.html"
+HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="os-specific"
></A
->4.4. OS Specific Installation Notes</H1
+>2.4. OS-Specific Installation Notes</H1
><P
>Many aspects of the Bugzilla installation can be affected by the
the operating system you choose to install it on. Sometimes it can be made
@@ -100,9 +100,9 @@ CLASS="section"
><A
NAME="os-win32"
></A
->4.4.1. Microsoft Windows</H2
+>2.4.1. Microsoft Windows</H2
><P
->Making Bugzilla work on windows is still a painful processes.
+>Making Bugzilla work on Windows is still a painful processes.
The Bugzilla Team is working to make it easier, but that goal is not
considered a top priority. If you wish to run Bugzilla, we still
recommend doing so on a Unix based system such as GNU/Linux. As of this
@@ -114,9 +114,9 @@ NAME="os-win32"
installing Bugzilla on Win32, here are some pointers.
Because this is a development version of the guide, these instructions
- are subject to change without notice. In fact, the Bugzilla Team hopes
- they do as we would like to have Bugzilla resonabally close to "out of
- the box" compatibility by the 2.18 release.
+ are subject to change without notice. In fact, the Bugzilla Team hopes
+ to have Bugzilla reasonably close to "out of
+ the box" compatibility with Windows by the 2.18 release.
</P
><DIV
@@ -126,7 +126,7 @@ CLASS="section"
><A
NAME="win32-perl"
></A
->4.4.1.1. Win32 Perl</H3
+>2.4.1.1. Win32 Perl</H3
><P
>Perl for Windows can be obtained from <A
HREF="http://www.activestate.com/"
@@ -147,12 +147,12 @@ CLASS="section"
><A
NAME="win32-perlmodules"
></A
->4.4.1.2. Perl Modules on Win32</H3
+>2.4.1.2. Perl Modules on Win32</H3
><P
>Bugzilla on Windows requires the same perl modules found in
<A
-HREF="stepbystep.html#install-perlmodules"
->Section 4.1.6</A
+HREF="installation.html#install-perlmodules"
+>Section 2.1.5</A
>. The main difference is that
windows uses <A
HREF="glossary.html#gloss-ppm"
@@ -219,38 +219,6 @@ TARGET="_top"
></TR
></TABLE
></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->A complete list of modules that can be installed using ppm can
- be found at <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus"
-TARGET="_top"
->http://www.activestate.com/PPMPackages/5.6plus</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
></DIV
><DIV
CLASS="section"
@@ -259,11 +227,11 @@ CLASS="section"
><A
NAME="win32-code-changes"
></A
->4.4.1.3. Code changes required to run on win32</H3
+>2.4.1.3. Code changes required to run on win32</H3
><P
>As Bugzilla still doesn't run "out of the box" on
- Windows, code has to be modified. This section is an attempt to
- list the required changes.
+ Windows, code has to be modified. This section lists the required
+ changes.
</P
><DIV
CLASS="section"
@@ -272,7 +240,7 @@ CLASS="section"
><A
NAME="win32-code-checksetup"
></A
->4.4.1.3.1. Changes to <TT
+>2.4.1.3.1. Changes to <TT
CLASS="filename"
>checksetup.pl</TT
></H4
@@ -359,12 +327,12 @@ CLASS="section"
><A
NAME="win32-code-bugmail"
></A
->4.4.1.3.2. Changes to <TT
+>2.4.1.3.2. Changes to <TT
CLASS="filename"
>BugMail.pm</TT
></H4
><P
->To make bug e-mail work on Win32 (until
+>To make bug email work on Win32 (until
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=84876"
TARGET="_top"
@@ -426,7 +394,7 @@ $smtp-&#62;quit;
></TABLE
><P
>Don't forget to change the name of your SMTP server and the
- domain of the sending e-mail address (after the '@') in the above
+ domain of the sending email address (after the '@') in the above
lines of code.</P
></DIV
></DIV
@@ -437,19 +405,19 @@ CLASS="section"
><A
NAME="win32-http"
></A
->4.4.1.4. Serving the web pages</H3
+>2.4.1.4. Serving the web pages</H3
><P
>As is the case on Unix based systems, any web server should be
able to handle Bugzilla; however, the Bugzilla Team still recommends
Apache whenever asked. No matter what web server you choose, be sure
to pay attention to the security notes in <A
-HREF="security.html#security-access"
->Section 4.5.4</A
+HREF="configuration.html#security-access"
+>Section 2.2.4.4</A
>.
More information on configuring specific web servers can be found in
<A
-HREF="http.html"
->Section 4.2</A
+HREF="configuration.html#http"
+>Section 2.2.4</A
>.
</P
><DIV
@@ -478,7 +446,7 @@ HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>ScriptInterpreterSource</A
>
- directive in your Apache config, if you don't do this, you'll have
+ directive in your Apache config to avoid having
to modify the first line of every script to contain your path to
perl instead of <TT
CLASS="filename"
@@ -498,17 +466,15 @@ CLASS="section"
><A
NAME="os-macosx"
></A
->4.4.2. <SPAN
+>2.4.2. <SPAN
CLASS="productname"
>Mac OS X</SPAN
></H2
><P
->There are a lot of common libraries and utilities out there that
- Apple did not include with Mac OS X, but which run perfectly well on it.
- The GD library, which Bugzilla needs to do bug graphs, is one of
- these.</P
+>Apple did not include the GD library with Mac OS X. Bugzilla
+ needs this for bug graphs.</P
><P
->The easiest way to get a lot of these is with a program called
+>You can install it using a program called
Fink, which is similar in nature to the CPAN installer, but installs
common GNU utilities. Fink is available from
<A
@@ -518,7 +484,10 @@ TARGET="_top"
>.</P
><P
>Follow the instructions for setting up Fink. Once it's installed,
- you'll want to use it to install the gd2 package.
+ you'll want to use it to install the <TT
+CLASS="filename"
+>gd2</TT
+> package.
</P
><P
>It will prompt you for a number of dependencies, type 'y' and hit
@@ -530,7 +499,7 @@ CLASS="glossterm"
>CPAN</I
></A
> to
- install the GD perl module.
+ install the GD Perl module.
</P
><DIV
CLASS="note"
@@ -587,7 +556,7 @@ CLASS="filename"
></TABLE
></DIV
><P
->Also available via Fink is expat. Once running using fink to
+>Also available via Fink is expat. After using fink to
install the expat package you will be able to install
XML::Parser using CPAN. There is one caveat. Unlike recent versions of
the GD module, XML::Parser doesn't prompt for the location of the
@@ -692,7 +661,7 @@ CLASS="section"
><A
NAME="os-mandrake"
></A
->4.4.3. Linux-Mandrake 8.0</H2
+>2.4.3. Linux-Mandrake 8.0</H2
><P
>Linux-Mandrake 8.0 includes every required and optional library
for Bugzilla. The easiest way to install them is by using the
@@ -780,7 +749,7 @@ BORDER="0"
ALT="(1)"></A
></DT
><DD
->for Bugzilla e-mail integration</DD
+>for Bugzilla email integration</DD
></DL
></DIV
></DIV
@@ -819,7 +788,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="security.html"
+HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -835,7 +804,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
-HREF="installation.html"
+HREF="installing-bugzilla.html"
ACCESSKEY="U"
>Up</A
></TD
@@ -843,7 +812,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Bugzilla Security</TD
+>Troubleshooting</TD
></TR
></TABLE
></DIV
generated by cgit v1.2.1 (git 2.21.0) at 2024-11-23 13:06:13 +0000