Comments on: Re: Wacky ideas #9: rerun maintainer scripts for changes in related packages http://blog.incase.de/index.php/2006/10/27/re-wacky-ideas-9-rerun-maintainer-scripts-for-changes-in-related-packages/ Sven's occasional log Mon, 23 Aug 2010 22:28:38 +0200 http://wordpress.org/?v=2.8.4 hourly 1 By: Ted http://blog.incase.de/index.php/2006/10/27/re-wacky-ideas-9-rerun-maintainer-scripts-for-changes-in-related-packages/comment-page-1/#comment-3 Ted Sat, 28 Oct 2006 00:39:06 +0000 http://blog.incase.de/index.php/2006/10/27/re-wacky-ideas-9-rerun-maintainer-scripts-for-changes-in-related-packages/#comment-3 I'd be inclined to remove the (removal|update|install) directory and instead make that an argument to the script, because there is likely to be a lot of duplicated code for each action. Consider init scripts or {pre,post}{inst,rm} scripts. Sounds quite good though. I believe ifupdown or resolvconf provides a similar mechanism, whereby squid (for instance) is reloaded when the network state changes. I'm not the maintainer of any packages with daemon-dependencies though :) I’d be inclined to remove the (removal|update|install) directory and instead make that an argument to the script, because there is likely to be a lot of duplicated code for each action. Consider init scripts or {pre,post}{inst,rm} scripts.

Sounds quite good though. I believe ifupdown or resolvconf provides a similar mechanism, whereby squid (for instance) is reloaded when the network state changes.

I’m not the maintainer of any packages with daemon-dependencies though :)

]]>