Add bat build doc

diff --git a/docs/manuals/en/main/install.tex b/docs/manuals/en/main/install.tex
index 25d9a701418394449c0f5a2c8c824c7cb3019094..8184e0d29deb16f45e35116df9c11acec671bae6 100644 (file)
--- a/docs/manuals/en/main/install.tex
+++ b/docs/manuals/en/main/install.tex
@@ -27,50 +27,41 @@ them.
  the Bacula SVN. The released files are:
 
 \begin{description}
-\item [bacula-3.0.3.tar.gz]
+\item [bacula-5.0.0.tar.gz]
   This is the primary source code release for Bacula. On each
-  release the version number (3.0.3) will be updated.
+  release the version number (5.0.0) will be updated.
 
-\item [bacula-docs-3.0.3.tar.gz]
+\item [bacula-docs-5.0.0.tar.bz2]
   This file contains a copy of the docs directory with the
   documents prebuild. English HTML directory, single HTML
-  file, and pdf file. The French and German translations
+  file, and pdf file. The French, German, Spanish translations
   are in progress, but are not built.
 
-\item [bacula-gui-3.0.3.tar.gz]
+\item [bacula-gui-5.0.0.tar.gz]
   This file contains the non-core GUI programs. Currently,
   it contains bacula-web, a PHP program for producing management
   viewing of your Bacula job status in a browser; and bimagemgr
   a browser program for burning CDROM images with Bacula Volumes.
 
-\item [bacula-rescue-3.0.3.tar.gz]
-  This is the Bacula Rescue CDROM code. Note, the version number
-  of this package is not tied to the Bacula release version, so
-  it will be different.  Using this code, you can burn a CDROM
+\item [bacula-rescue-5.0.0.tar.gz]
+  This is the Bacula Rescue USB key code. Note, the version number
+  of this package is not always tied to the Bacula release version, so
+  it may be different.  Using this code, you can create a USB key
   with your system configuration and containing a statically
   linked version of the File daemon. This can permit you to easily
   repartition and reformat your hard disks and reload your
   system with Bacula in the case of a hard disk failure.
-  Unfortunately this rescue disk does not properly boot for
-  all Linux distributions. The problem is that the boot procedure
-  can vary significantly between distributions, and even within
-  a distribution, they are a moving target.
-
-  This package evolves slower than the Bacula source code,
-  so there may not always be a new release of the rescue package when
-  making minor updates to the Bacula code. For example, when releasing
-  Bacula version 3.0.3, the rescue package may still be at a prior
-  version if there were no updates.
-
-\item [winbacula-3.0.3.exe]
+
+\item [win32bacula-5.0.0.exe]
   This file is the 32 bit Windows installer for installing
   the Windows client (File daemon) on a Windows machine.
-  This client will also run on 64 bit Windows machines.
-  Beginning with Bacula version 1.39.20, this executable will
-  also optionally load the Win32 Director and the Win32 
-  Storage daemon.
+  This client will also run on 64 bit Windows machines, but
+  VSS support is not available if you are running a 64 bit
+  version of Windows.  This installer installs only the FD, 
+  the Director and Storage daemon are not included.
+
 
-\item [win64bacula-3.0.3.exe]
+\item [win64bacula-5.0.0.exe]
   This file is the 64 bit Windows installer for installing
   the Windows client (File daemon) on a Windows machine.
   This client will only run on 64 bit Windows OS machines.
@@ -272,7 +263,7 @@ for compatibility with Bacula.
 Typically, a dependency package will be named {\bf depkgs-ddMMMyy.tar.gz}
 where {\bf dd} is the day we release it, {\bf MMM}
 is the abbreviated month (e.g. Jan), and {\bf yy} is the year. An actual
-example is: {\bf depkgs-24Jul09.tar.gz}. To install and build this package (if
+example is: {\bf depkgs-18Dec.tar.gz}. To install and build this package (if
 needed), you do the following: 
 
 \begin{enumerate}
@@ -317,6 +308,47 @@ You should build the packages that you will require in {\bf depkgs} a
 prior to configuring and building Bacula, since Bacula will need
 them during the build process. 
 
+Note, the {\bf depkgs-qt} package is required for building bat, because 
+bat is currently built with Qt version 4.3.4.  It can be built with other
+Qt versions, but that almost always creates problems or introduces
+instabilities.
+
+You can build the depkgs-qt with the following:
+
+\footnotesize
+\begin{verbatim}
+cd bacula
+tar xfvz depkgs-qt-28Jul09.tar.gz
+cd depkgs-qt
+make qt4
+source qt4-path
+\end{verbatim}
+\normalsize
+
+Doing the {\bf source qt4-path} defines the following environment
+variables:
+
+\footnotesize
+\begin{verbatim}
+QTDIR
+QTLIB
+QTINC
+\end{verbatim}
+\normalsize
+
+Each one should point to a specific location in the depkgs-qt package
+that you loaded.  It also puts the depkgs-qt/qt4/bin directory
+on your path before all other directories.  This ensures that
+the bat build will use your Qt 4.3.4 library rather than any that 
+might be on your system.
+
+Before running your Bacula build, please make sure that
+{\bf qmake-qt4} is not on your path.  If it is please rename it. If
+you don't do this, Bacula will attempt to build with any Qt4 package
+installed on your system rather than the one you just built.
+If you logoff and log back in, you must re-source the depkgs-qt/qt4-patch
+file before attempting to rebuild the bat part of Bacula.
+
 For more information on the {\bf depkgs-qt} package, please read the
 INSTALL file in the main directory of that package. If you are going to 
 build Qt4 using {\bf depkgs-qt}, you must source the {\bf qt4-paths} file