>>>>> On Mon, 16 Aug 2010 15:31:32 +0200, Bruno Friedmann said: > > Hi all. > > Trying to build the "most not bad package" I'm trying to understand what I > need to do to have a good > bacula-lib rpm. > > I'm in the process to conclude that I need two separated package which > conflict each others > bacula-client + bacula-client-libs > conflict > bacula-mysql + bacula-mysql-libs > bacula-sqlite + bacula-sqlite-libs > bacula-postgrsql + bacula-postgresql-libs
Why are the bacula-$dbtype-libs packages needed? It might be better to put libbacsql into bacula-$dbtype since nothing else can depend on it (right?). Then bacula-client and bacula-$dbtype can depend on bacula-libs like they do now. > Also I didn't understand why I finish with a batch-insert-enable = no with > mysql & postgresql even if I specify the > --enable-batch-insert at ./configure For postgresql, check the configure output for: checking for PQisthreadsafe in -lpq... yes checking for PQputCopyData in -lpq... yes If either of these says "no" then batch insert will be switched off. __Martin ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
