[Dbconfig-common-devel] Re: dbconfig-common - short question

[sean finney]

hi marcin,

please, keep the dbconfig list in the CC field... as others
may benefit from this as well.

On Thu, Feb 09, 2006 at 02:14:11AM +0100, Marcin Antczak wrote:
> no, what should happen is when they install the package, they get an
> > error message saying "can not connect to mysql server, what would
> > you like to do?"
> 
> 
> And then what? User doesn't have choice in fact. Because he always has to
> break installation, leave package unconfigured (broken) and then he propably
> could install mysql-server.

not quite true.  in this case, they would need to choose either "abort",
which would leave the package unconfigured, or "ignore", which would
let the installation finish.  in both cases they could then install
mysql-server.  in the first case, i believe that dpkg would
automatically attempt to configure the half-configured package (but
i'm not positive) after mysql-server was installed.  but in any case
one could try again with dpkg-reconfigure or removing/reinstalling
the package.

> nope... the current default on debian systems is to install mysql-server
> > with a passwordless root account.  so... if we're dealing with osmeone
> > who doesn't know what's going on then they'll just hit enter when
> > prompted for the admin password, and things will still work.
> 
> 
> Hmm I need to try this too. I use Ubuntu so maybe this is different.

being a co-maintainer for mysql, i can tell you that it's the
same.  at least, it doesn't show up in the list of ubuntu
diffs and installing mysql-server on my kubuntu laptop seems
to confirm this.

> > i think such a behaviour is probably better a "global" option, that is
> > the answer "yes use debian.cnf" for installing one package will probably
> > be the same for any othermysql package installed.  so then what would
> > probably be simplest is to put in dbc's config script something like:
> >
> > if -f debian.cnf
> >         prompt if i should use it
> >
> > and then write the result into /etc/dbconfig-common/config
> > during postinst.  then the dbc helper scripts that run for individual
> > packages could check the setting from this file and if it's set to true
> > run mysql commands
> > with --defaults-extra-file=debian.cnf.
> 
> 
> VERY good idea.

well, as i said before... patches doing this are welcome.  if
you're motivated to do this i suggest you contact me over
irc/icq/im (i'll send to you privately) and we can chat about the
specifics of what would need to be done.

> I understand pretty much of dbconfig-common code. So, I think that your idea
> about /etc/mysq/debian.cnf as $mycnf is very good. But also I thought about
> another thing - my idea was to add format that is in debian.cnf as format
> supported by dbconfig-load-include. And just load this file.

two things:

- supporting the "ini"-style format would be a good and useful
  feature for d-l-i and d-g-i.
- but... you would not want to use debian.cnf through dbc-load-include.
  this file has administrative credentials, and at the very most it should
  only be used for adding/removing users/databases.  everything else
  should be done using the privileges of the user created for the package.


	sean

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20060209/0d4d4bbc/attachment.pgp