projects / invirt/packages/xvm-prodconfig.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2b4a276) | patch
Run invirt-reload directly in the postinst of the fooconfig packages. 1.1.20
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)
commit603acfdf9ff66fc3cff44550c3443954d3a437f5
tree6d5db727a2dbb73ce662df0726cf743cedbbd82ftree | snapshot
parent2b4a276e6a366127939ad7111ac3d78a1d121f39commit | diff
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/xvm-prodconfig/; revision=2940
debian/changelog diff | blob | history
debian/xvm-prodconfig.postinst [new file with mode: 0755] blob
debian/xvm-prodconfig.triggers [deleted file] blob | history
Unnamed repository; edit this file 'description' to name the repository.