Re: dkms needs a pre-depends entry (Policy 3.5)
Russ Allbery writes ("Re: dkms needs a pre-depends entry (Policy 3.5)"):
> Bernd Zeimetz <firstname.lastname@example.org> writes:
> > It should as you can't assume that your dependencies are configured when
> > your own package is being configured (Debian Policy 3.5).
> That's not correct. You can assume that your dependencies are configured
> before you're configured unless there are circular dependencies involved.
Right. The difficulty here is that if you both depend on a package
and trigger it in your postinst, when your postinst starts the package
is configured, but when you trigger it, it stops being configured but
your postinst is still running.
You have to deal with that case yourself somehow. The package you're
triggering and depending on should provide a synchronous way for you
to force your addons to that package to be ready for use by you right
now, as well as just the trigger (which is a way to make sure they'll
be ready for other people).