Changeset 2940


Ignore:
Timestamp:
Jan 27, 2010, 9:53:04 PM (15 years ago)
Author:
broder
Message:

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.

Location:
trunk/packages
Files:
4 added
4 deleted
3 edited

Legend:

Unmodified
Added
Removed

  • trunk/packages/hvirt-config/debian/changelog

    r2924 r2940  
     1hvirt-config (0.0.18) unstable; urgency=low
     2
     3  * Run invirt-reload in the postinsts, not using triggers.
     4
     5 -- Evan Broder <broder@mit.edu>  Wed, 27 Jan 2010 21:20:00 -0500
     6
    17hvirt-config (0.0.17) unstable; urgency=low
    28

  • trunk/packages/xvm-devconfig/debian/changelog

    r2925 r2940  
     1xvm-devconfig (0.51) unstable; urgency=low
     2
     3  * Run invirt-reload in the postinsts, not using triggers.
     4
     5 -- Evan Broder <broder@mit.edu>  Wed, 27 Jan 2010 21:20:13 -0500
     6
    17xvm-devconfig (0.50) unstable; urgency=low
    28

  • trunk/packages/xvm-prodconfig/debian/changelog

    r2938 r2940  
     1xvm-prodconfig (1.1.20) unstable; urgency=low
     2
     3  * Run invirt-reload in the postinsts, not using triggers.
     4
     5 -- Evan Broder <broder@mit.edu>  Wed, 27 Jan 2010 21:20:08 -0500
     6
    17xvm-prodconfig (1.1.19) unstable; urgency=low
    28
Note: See TracChangeset for help on using the changeset viewer.