Re: Using debconf to notify of serious postinst problems
-----BEGIN PGP SIGNED MESSAGE-----
Roberto C. Sánchez wrote:
> On Fri, Mar 23, 2007 at 01:42:30PM +0000, Colin Turner wrote:
>> 2. Using debconf to notify in postinst
> Hi. I'm not sure of the details of your software (I've not looked at
> it), but I will offer my recommendation as to the database issue.
> Consider that installation may happen unattended. If so, how will the
> admin be prompted? I am not up to speed on my debconf-fu. However, I
> would recommend that you differentiate between an interactive and a
> non-interactive installation. In either case, you should include a
> script in some place like /usr/share/doc/opus/scripts (or something like
> that) called schema.mysql (or just .sql if it is generic enough to work
> on other servers).
I guess I was thinking that a) it's not unusual for dist-upgrades and so
on to halt on postinst due to config files and other issues and b)
debconf can send notes as emails if it doesn't show them to the end
user. I wasn't sure though, hence the question :-).
Nevertheless, that's a good idea. I already place the schema in
/usr/share/doc/sql_patch/ and that's where my shell script installs it
from. I can add manual instructions too. Neil's suggestion
(dbconfig-common) might take care of all of this anyway.
> You may also want to consider adding a /etc/defaults/opus with an
> "ENABLED=YES|NO" sort of option and have the startup or init script
> check that. Then if the install is unattended, the admin has to go in
> later, create the databases and set the ENABLED variable in the defaults
That's a very good plan indeed. I'll look at that along with Neil's
Thanks for your time!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----