Hi Paul, On 07/01/2016 08:43 AM, Paul Gevers wrote: > On 30-06-16 23:39, Christian Seiler wrote: >> Does this give you an idea of what I have in mind? > > Just thinking, would it make sense to enable dbconfig-common outside of > the normal package postinst, such that it can use all the data, and just > runs as if it was during the normal postinst? It looks like that script > is nearly the script that you need.
I think so, yes. > Do you object if we would just always create the script if > configuration fails? In certain circumstances. I don't remember exactly what happens at the moment if you misspell the host name (because that was too long ago that that has happened to me), but IIRC dbconfig would either re-ask the question of fail configure, so the admin would have a significant feedback in that case. If you change this to just silently create the script, then admins might not notice that configuration failed (especially if they are installing a ton of packages at the same time). So if you properly handle this in some way (whichever you believe to be most appropriate), so that this change doesn't blind-side admins that expect feedback if something goes wrong then I'd be OK with it. Regards, Christian
