Comment 13 for bug 1225

On Thu, 2007-02-15 at 09:33 +0000, Martin Pitt wrote:
> > One problem you probably do have is that the regular debian/Ubuntu
> > postgres installation causes a postgres instance to be run at start up
> > (though the user can stop it in the Services control panel). That makes
> > sense if you install postgres directly, but it's not needed or used by
> > Glom.

Thanks for the response.

> I am not going to change this -- people installing PostgreSQL usually do
> so because they want to use it,

This will not change when people are using Glom.

The assumption you are actually making is "people installing PostgreSQL
usually want to configure it how it is currently configured". But things
change.

> and Debian's/Ubuntu's philosophy is that
> things should 'just work' without fiddling with unnecessary
> configuration.
>
> As a compromise, I propose this: glom Recommends: postgresql-8.2, so
> that it is handled as a dependency by all the standard packaging
> frontends, but if people know what they are doing, they can avoid
> installing it.

By default, synaptic does not install "recommends" packages.

> Glom should then check for the availability of pg_createcluster and use
> it to create a cluster that belongs to the user invoking glom. If
> pg_createcluster is not available, glom should ask the user to install a
> postgresql server.

This is not "just work". This is "Do something extra that I don't
understand, with several ways to get it wrong, so that the application
does something useful and obvious".

This "The application that you have installed is not fully installed"
dialog will be the first experience of 99.9% of all people using Glom.
And I plan for that to be a lot of people.

--
Murray Cumming
<email address hidden>
www.murrayc.com
www.openismus.com