On Tue, Apr 21, 2009 at 12:19:30PM +0200, Mariusz Mazur wrote: > Bacula uses a database backend, but can be compiled only against one database > at a time. The default in pld was mysql. > > Recently released Bacula 3.0 adds support for libdbi, which, in short, is a > database abstraction layer with runtime db plugins (called drivers), so > bacula compiled with libdbi supports any database without the need to > recompile anything (you just install bacula + libdbi and add e.g. > libdbi-drivers-mysql to the mix). This is obviously what we need to have as a > default in pld. > > Problem: if we make the switch, any old configuration which depends on bacula > being compiled natively against mysql will stop working. The fix will most > likely be extremely trivial, yet, I doubt many people will be happy that > we're breaking something as crucial as a backup system. > > So, anybody got any ideas how to handle this properly? Would a %banner be > enough stating that you need to a) add libdbi-drivers-mysql and b) alter the > config? Or maybe something else?
%banner is enough for me Cheers, Arek _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
