Run invirt-reload directly in the postinst of the fooconfig packages.
authorEvan Broder <broder@mit.edu>
Thu, 28 Jan 2010 02:53:04 +0000 (21:53 -0500)
committerEvan Broder <broder@mit.edu>
Thu, 28 Jan 2010 02:53:04 +0000 (21:53 -0500)
commitaf3453936f4dbe125a6b9fadbe086fc6972b47ce
treeaed1fe8f0b72ae8f18e0aaaaefc08ed8f10822e3
parent94e92a94999051963998214e475e6e9637ebe9c1
Run invirt-reload directly in the postinst of the fooconfig packages.

This replaces the old mechanism of using triggers. Activating triggers
via a package.triggers file doesn't seem to have taken off in the
Debian/Ubuntu communities.

Instead, the standard approach seems to be to run the triggered
command as usual, and add logic to the triggered command to postpone
actually running itself until later.

svn path=/trunk/packages/hvirt-config/; revision=2940
debian/changelog
debian/hvirt-devconfig.postinst [new file with mode: 0755]
debian/hvirt-devconfig.triggers [deleted file]
debian/hvirt-prodconfig.postinst [new file with mode: 0755]
debian/hvirt-prodconfig.triggers [deleted file]