From 470e008c23ae0338dd4a18781530e518232286d0 Mon Sep 17 00:00:00 2001
From: Simone Caronni <negativo17@gmail.com>
Date: Mar 08 2017 12:16:36 +0000
Subject: Update README.Redhat document


---

diff --git a/README.Redhat b/README.Redhat
index cdb6109..a6b9ca2 100644
--- a/README.Redhat
+++ b/README.Redhat
@@ -26,10 +26,39 @@ backends:
 - quickstart_postgresql.txt
 - quickstart_sqlite3.txt
 
-To deal with the switching process for the database backend, see the following
-file which explains how to make the necessary changes:
+======== PostgreSQL, MySQL and SQLite databases
 
-- database_backends.txt
+Bacula director supports different databases backends, if you want to switch
+away from the default PostgreSQL one you need to change the "libbaccats" (the
+catalogue library) symlink to the real library.
+
+To change to a different backend, issue the following command:
+
+# alternatives --config libbaccats.so
+
+There are 3 programs which provide 'libbaccats.so'.
+
+  Selection    Command
+-----------------------------------------------
+   1           /usr/lib64/libbaccats-mysql.so
+   2           /usr/lib64/libbaccats-sqlite3.so
+*+ 3           /usr/lib64/libbaccats-postgresql.so
+
+Enter to keep the current selection[+], or type selection number: 1
+
+There is NO need to edit any part in the Bacula Director configuration; for the
+purposes of the database creation steps, the bacula-dir.conf configuration file
+can be left at their default values.
+
+======== Switiching between PostgreSQL, MySQL and SQLite backends
+
+To switch the configured backend to another one, follow the above procedure.
+Again, there's no need to edit the Bacula Director configuration file; the
+catalog resource can be left as is.
+
+Importing and exporting data between the various database formats is up to the
+user. If the database will be re-initialized from scratch, follow the quick
+start guides mentioned above.
 
 ======== Upgrading from old Redhat releases
 
diff --git a/bacula.spec b/bacula.spec
index dd7fa3b..9657d27 100644
--- a/bacula.spec
+++ b/bacula.spec
@@ -3,7 +3,7 @@
 
 Name:               bacula
 Version:            7.4.5
-Release:            1%{?dist}
+Release:            2%{?dist}
 Summary:            Cross platform network backup for Linux, Unix, Mac and Windows
 # See LICENSE for details
 License:            AGPLv3 with exceptions
@@ -777,6 +777,9 @@ fi
 %{_libdir}/nagios/plugins/check_bacula
 
 %changelog
+* Wed Mar 08 2017 Simone Caronni <negativo17@gmail.com> - 7.4.5-2
+- Update README.Redhat document.
+
 * Wed Feb 08 2017 Simone Caronni <negativo17@gmail.com> - 7.4.5-1
 - Update to 7.4.5.
 - Update patches.
diff --git a/database_backends.txt b/database_backends.txt
deleted file mode 100644
index 024cc68..0000000
--- a/database_backends.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-======== PostgreSQL, MySQL and SQLite databases
-
-Bacula director supports different databases backends, if you want to switch
-away from the default PostgreSQL one you need to change the "libbaccats" (the
-catalogue library) symlink to the real library.
-
-To change to a different backend, issue the following command:
-
-# alternatives --config libbaccats.so
-
-There are 3 programs which provide 'libbaccats.so'.
-
-  Selection    Command
------------------------------------------------
-   1           /usr/lib64/libbaccats-mysql.so
-   2           /usr/lib64/libbaccats-sqlite3.so
-*+ 3           /usr/lib64/libbaccats-postgresql.so
-
-Enter to keep the current selection[+], or type selection number: 1
-
-There is NO need to edit any part in the Bacula Director configuration; for the
-purposes of the database creation steps, the bacula-dir.conf configuration file
-can be left at their default values.
-
-======== Switiching between PostgreSQL, MySQL and SQLite backends
-
-To switch the configured backend to another one, follow the above procedure.
-Again, there's no need to edit the Bacula Director configuration file; the
-catalog resource can be left as is.
-
-Importing and exporting data between the various database formats is up to the
-user. If the database will be re-initialized from scratch, follow the quick
-start guides mentioned above.