Add SuSE-11.0

diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex
index 8ffc2e5dddfef960c2f9507969925784d8273f5f..76bcfe6e092973b63426b97661369e3ee94b6c07 100644 (file)
--- a/docs/manual/rpm-faq.tex
+++ b/docs/manual/rpm-faq.tex
@@ -41,9 +41,9 @@
    {\bf How do I build Bacula for platform xxx?}
    The bacula spec file contains defines to build for several platforms:
    Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), Fedora Core (fc1,
-   fc3, fc4, fc5, fc6, fc7), Whitebox Enterprise Linux 3.0 (wb3), Red Hat Enterprise Linux 
+   fc3, fc4, fc5, fc6, fc7, fc8), Whitebox Enterprise Linux 3.0 (wb3), Red Hat Enterprise Linux 
    (rhel3, rhel4, rhel5), Mandrake 10.x (mdk), Mandriva 2006.x (mdv) CentOS (centos3, centos4, centos5) 
-   Scientific Linux (sl3, sl4, sl5) and SuSE (su9, su10, su102, su103). The package build is controlled by a mandatory define set at the beginning of the file.  These defines basically just control the dependency information that gets coded into the finished rpm package as well 
+   Scientific Linux (sl3, sl4, sl5) and SuSE (su9, su10, su102, su103, su110). The package build is controlled by a mandatory define set at the beginning of the file.  These defines basically just control the dependency information that gets coded into the finished rpm package as well 
    as any special configure options required.  The platform define may be edited 
    in the spec file directly (by default all defines are set to 0 or "not set").  
    For example, to build the Red Hat 7.x package find the line in the spec file
@@ -315,6 +315,7 @@ SuSE build
 --define "build_su10 1"
 --define "build_su102 1"
 --define "build_su103 1"
+--define "build_su110 1"
 
 Mandrake 10.x build
 --define "build_mdk 1"