Bug#289838: Creating databases for the bacula-director

[José Luis Tallón]

Joerg Friedrich wrote:
Hi,
just a hint, maybe I have the time to look deeper into it at the
weekend.
Don't reinvent the wheel when creating databases in postinst, resp.
removing them on purge. Use the wwwconfig-common framework.
 

No, that is not an option right now:
- wwwconfig-common is *deprecated* for DB-related config
- we are too close to a release
The package name might be misleading the package supports additionally
to manipulating the apache and php config also creating and
removing of database, user... for mysql and postgres.
 

Yes, I know. That is why is proposed a migration to *dbconfig-common* 
[which was designed precisely for this purpose] long ago.

These packages have rdepends on wwwconfig-common. most of them just use
it for configuring apache and php, but some of them to create databases
and db users. Esp. horde2 is a very good one.
 

Well, those packages will start receiving RC bugs to get them migrated 
to wwwconfig-common + dbconfig-common (or just one of them, as 
appropiate), as soon as dbconfig-common has been completely tested 
(specially by means of a series of "experimental" bacula-director 
package releases) and Sarge has been released.

Sorry if i sounded too harsh, but there is no way that i can get 
everything migrated with so little time. And then, wwwconfig-common is 
quite a mess to be used in Bacula's postinst scripts -- dbconfig-common 
is the way to go.
Anyways, your attention and suggestion is very much appreciated. Please 
keep the feedback coming.

Best,
   J.L.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]