Re: Finding out in postinst whether some other package is configured
On Tue, 2005-10-11 at 19:28 +0200, Frank Küster wrote:
> is there an established way to find out in the postinst script of a
> package whether an other package (e.g. one which we Recommend or
> Suggest) is configured? Testing for file contents can only tell whether
> it is unpacked, but that might not be enough.
> If there isn't, are there other people who felt the need to know this?
I worry about why you would need to know this. I'm envisioning a
package "A" that has a particular default configuration if you install A
before B, but a different configuration if you install B before A. What
will the user be missing out on if they're installed in the "wrong"
order? And what corrective action can the user take?