Re: RFC: best practice creating database
On Fri, 8 Oct 2004 15:26:41 +0200
uwe@steinmann.cx (Uwe Steinmann) wrote:
> On Fri, Oct 08, 2004 at 03:45:26PM +1000, Andrew Pollock wrote:
> > On Thu, Oct 07, 2004 at 05:19:07PM +0200, Uwe Steinmann wrote:
> > > On Thu, Oct 07, 2004 at 03:38:59PM +0200, Philipp Matthias Hahn wrote:
> > > > Hello!
> > > >
> > > > What is consideres best practice when a package uses a SQL database
> > > > (mysql, postgresql) and needs to create its own catalog and/or tables?
> > > >
> > > > [ ] Disable the package until someone has manually setup the database?
> > > > [ ] Ask a lot of questions via debconf and try to setup in postconf?
> > > I'd go for the second option.
> > >
> > [snip]
> > >
> > > Setting up a database is somewhat errorprune but still something
> > > achievable in a postinst script.
> >
> > Methinks we need something like wwwconfig-common, but for databases...
> wwwconfig-common does most of what needs to be done for setting
> up a database. What are you missing?
First of all documentation.
Bye
Racke
--
Debian maintainer of Courier, Pure-FTPd, Interchange, Sympa
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
Reply to: