Hi Christian, 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. E.g. the script that you are thinking of is essentially just: "dbc_go $package configure" So creating the script then becomes rather easy, because we basically just need to fill in some dbconfig variables and all would be well. I believe the only thing that would than be further required is "just" documentation and some minor changes to templates. Do you object if we would just always create the script if configuration fails? It doesn't store any sensitive stuff on its own anyways, just a subset of the postinst stuff of the package in question. Paul
signature.asc
Description: OpenPGP digital signature
