Re: dkms needs a pre-depends entry (Policy 3.5)
Bernd Zeimetz <firstname.lastname@example.org> writes:
> Lets remove all triggers from dpkg then.
For things that have to run to make the package usable, yes.
> Updating the Python modules for every new module package is a big waste
> of time, running it as a trigger results into the described problem in a
> few rare cases. What do you prefer?
I prefer packages to work after they've been configured. Otherwise,
Depends doesn't do what it's supposed to do. Triggers are great for
things that aren't required for the package to function (updating the man
database, updating the doc-base index, registering newly-installed fonts
with other subsystems), but if an action is required for basic package
functionality, I don't think you can safely use triggers.
> Also adding update-python-modules -p to a postinst script does not hurt,
> even when dependencies change.
This is true, but one shouldn't have to configure another package if one
already depended on it.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>