summaryrefslogtreecommitdiffstats
path: root/docs/html/os-specific.html
diff options
context:
space:
mode:
authorjustdave%syndicomm.com <>2004-02-05 13:49:08 +0100
committerjustdave%syndicomm.com <>2004-02-05 13:49:08 +0100
commit11945a73c631bedbcf8daaba531964c3fc2d6333 (patch)
tree6c23288dd801bd8a1bf9ad548eb9a4e82cd24eef /docs/html/os-specific.html
parentcfc778d1fc757e022c0755ccc5ecd430790ce8be (diff)
downloadbugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.gz
bugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.xz
- Remove html, txt, and pdf directories from CVS
- makedocs.pl now creates said directories when building the docs The idea here is that it's useless to have compiled stuff in CVS. The website will now auto-build the docs upon changes to the xml directory.
Diffstat (limited to 'docs/html/os-specific.html')
-rw-r--r--docs/html/os-specific.html821
1 files changed, 0 insertions, 821 deletions
diff --git a/docs/html/os-specific.html b/docs/html/os-specific.html
deleted file mode 100644
index 224651cf2..000000000
--- a/docs/html/os-specific.html
+++ /dev/null
@@ -1,821 +0,0 @@
-<HTML
-><HEAD
-><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.7
- Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installing Bugzilla"
-HREF="installing-bugzilla.html"><LINK
-REL="PREVIOUS"
-TITLE="Optional Additional Configuration"
-HREF="extraconfig.html"><LINK
-REL="NEXT"
-TITLE="Troubleshooting"
-HREF="troubleshooting.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.7
- Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Installing Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="os-specific"
-></A
->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
- easier and others more difficult. This section will attempt to help you
- understand both the difficulties of running on specific operating systems
- and the utilities available to make it easier.
- </P
-><P
->If you have anything to add or notes for an operating system not
- covered, please file a bug in <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->Bugzilla Documentation</A
->.
- </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="os-win32"
-></A
->2.4.1. Microsoft Windows</H2
-><P
->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
- writing, all members of the Bugzilla team and all known large installations
- run on Unix based systems.
- </P
-><P
->If after hearing all that, you have enough pain tolerance to attempt
- 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
- to have Bugzilla reasonably close to "out of
- the box" compatibility with Windows by the 2.18 release.
-
- </P
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="win32-perl"
-></A
->2.4.1.1. Win32 Perl</H3
-><P
->Perl for Windows can be obtained from <A
-HREF="http://www.activestate.com/"
-TARGET="_top"
->ActiveState</A
->. You should be
- able to find a compiled binary at <A
-HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
-TARGET="_top"
->http://aspn.activestate.com/ASPN/Downloads/ActivePerl/</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="win32-perlmodules"
-></A
->2.4.1.2. Perl Modules on Win32</H3
-><P
->Bugzilla on Windows requires the same perl modules found in
- <A
-HREF="installation.html#install-perlmodules"
->Section 2.1.5</A
->. The main difference is that
- windows uses <A
-HREF="glossary.html#gloss-ppm"
-><I
-CLASS="glossterm"
->PPM</I
-></A
-> instead of
- CPAN.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;C:\perl&#62; <B
-CLASS="command"
->ppm &#60;module name&#62;</B
->
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The above syntax should work for all modules with the exception
- of Template Toolkit. The <A
-HREF="http://tt2.org/download.html#win32"
-TARGET="_top"
->Template Toolkit website</A
->
- suggests using the instructions on <A
-HREF="http://openinteract.sourceforge.net/"
-TARGET="_top"
->OpenInteract's website</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="win32-code-changes"
-></A
->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 lists the required
- changes.
- </P
-><DIV
-CLASS="section"
-><H4
-CLASS="section"
-><A
-NAME="win32-code-checksetup"
-></A
->2.4.1.3.1. Changes to <TT
-CLASS="filename"
->checksetup.pl</TT
-></H4
-><P
->In <TT
-CLASS="filename"
->checksetup.pl</TT
->, the line reading:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;my $mysql_binaries = `which mysql`;
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->to</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;my $mysql_binaries = "D:\\mysql\\bin\\mysql";
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->And you'll also need to change:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;my $webservergid = getgrnam($my_webservergroup)
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->to</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;my $webservergid = '8'
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><H4
-CLASS="section"
-><A
-NAME="win32-code-bugmail"
-></A
->2.4.1.3.2. Changes to <TT
-CLASS="filename"
->BugMail.pm</TT
-></H4
-><P
->To make bug email work on Win32 (until
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=84876"
-TARGET="_top"
->bug
- 84876</A
-> lands), the
- simplest way is to have the Net::SMTP Perl module installed and
- change this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") ||
- die "Can't open sendmail";
-
-print SENDMAIL trim($msg) . "\n";
-close SENDMAIL;
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->to</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;use Net::SMTP;
-my $smtp_server = 'smtp.mycompany.com'; # change this
-
-# Use die on error, so that the mail will be in the 'unsent mails' and
-# can be sent from the sanity check page.
-my $smtp = Net::SMTP-&#62;new($smtp_server) ||
- die 'Cannot connect to server \'$smtp_server\'';
-
-$smtp-&#62;mail('bugzilla-daemon@mycompany.com'); # change this
-$smtp-&#62;to($person);
-$smtp-&#62;data();
-$smtp-&#62;datasend($msg);
-$smtp-&#62;dataend();
-$smtp-&#62;quit;
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->Don't forget to change the name of your SMTP server and the
- domain of the sending email address (after the '@') in the above
- lines of code.</P
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="win32-http"
-></A
->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="configuration.html#security-access"
->Section 2.2.4.4</A
->.
- More information on configuring specific web servers can be found in
- <A
-HREF="configuration.html#http"
->Section 2.2.4</A
->.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If using Apache on windows, you can set the <A
-HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
-TARGET="_top"
->ScriptInterpreterSource</A
->
- 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"
->/usr/bin/perl</TT
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="os-macosx"
-></A
->2.4.2. <SPAN
-CLASS="productname"
->Mac OS X</SPAN
-></H2
-><P
->Apple did not include the GD library with Mac OS X. Bugzilla
- needs this for bug graphs.</P
-><P
->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
-HREF="http://sourceforge.net/projects/fink/"
-TARGET="_top"
->http://sourceforge.net/projects/fink/</A
->.</P
-><P
->Follow the instructions for setting up Fink. Once it's installed,
- 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
- enter to install all of the dependencies and then watch it work. You will
- then be able to use <A
-HREF="glossary.html#gloss-cpan"
-><I
-CLASS="glossterm"
->CPAN</I
-></A
-> to
- install the GD Perl module.
- </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->To prevent creating conflicts with the software that Apple
- installs by default, Fink creates its own directory tree at
- <TT
-CLASS="filename"
->/sw</TT
-> where it installs most of
- the software that it installs. This means your libraries and headers be
- at <TT
-CLASS="filename"
->/sw/lib</TT
-> and
- <TT
-CLASS="filename"
->/sw/include</TT
-> instead of
- <TT
-CLASS="filename"
->/usr/lib</TT
-> and
- <TT
-CLASS="filename"
->/usr/local/include</TT
->. When the
- Perl module config script asks where your libgd is, be sure to tell it
- <TT
-CLASS="filename"
->/sw/lib</TT
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->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
- required libraries. When using CPAN, you will need to use the following
- command sequence:
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="screen"
->&#13;# perl -MCPAN -e'look XML::Parser' <A
-NAME="macosx-look"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
->
-# perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include
-# make; make test; make install <A
-NAME="macosx-make"
-><IMG
-SRC="../images/callouts/2.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(2)"></A
->
-# exit <A
-NAME="macosx-exit"
-><IMG
-SRC="../images/callouts/3.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(3)"></A
->
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="calloutlist"
-><DL
-COMPACT="COMPACT"
-><DT
-><A
-HREF="os-specific.html#macosx-look"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
-><A
-HREF="os-specific.html#macosx-exit"
-><IMG
-SRC="../images/callouts/3.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(3)"></A
-></DT
-><DD
->The look command will download the module and spawn a
- new shell with the extracted files as the current working directory.
- The exit command will return you to your original shell.
- </DD
-><DT
-><A
-HREF="os-specific.html#macosx-make"
-><IMG
-SRC="../images/callouts/2.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(2)"></A
-></DT
-><DD
->You should watch the output from these make commands,
- especially <SPAN
-CLASS="QUOTE"
->"make test"</SPAN
-> as errors may prevent XML::Parser
- from functioning correctly with Bugzilla.
- </DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="os-mandrake"
-></A
->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
- <B
-CLASS="command"
->urpmi</B
-> utility. If you follow these commands, you
- should have everything you need for Bugzilla, and
- <B
-CLASS="command"
->./checksetup.pl</B
-> should not complain about any
- missing libraries. You may already have some of these installed.
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="screen"
->&#13;<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->urpmi perl-mysql</B
->
-<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->urpmi perl-chart</B
->
-<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->urpmi perl-gd</B
->
-<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->urpmi perl-MailTools</B
-> <A
-NAME="test-mailtools"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
->
-<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->urpmi apache-modules</B
->
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="calloutlist"
-><DL
-COMPACT="COMPACT"
-><DT
-><A
-HREF="os-specific.html#test-mailtools"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
-></DT
-><DD
->for Bugzilla email integration</DD
-></DL
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Optional Additional Configuration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installing-bugzilla.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Troubleshooting</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file