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