On Thu, 22 May 2008, Niko Tyni wrote: > On Tue, May 20, 2008 at 10:10:02AM -0400, Noah Meyerhans wrote: > > There are a few different things that need to happen to spamassassin > > when perl is upgraded. Compiled rules need to be blown away and > > rebuilt, for example. Unfortunately, perl is in a much better position > > than we are to know when it's upgraded. Perhaps perl should take care > > of triggering a spamassassin restart, similar to what glibc does... > > This is also #230308 against perl. > > Although there's the glibc precedent, the perl package doesn't really > want to know which packages need a restart. I wonder if the new dpkg > triggers would be a good solution for this.
No, the only way triggers could be used would be if spamassasin was triggered on update of /usr/bin/perl and it would have no way to know if it's a major upgrade (5.8 -> 5.10) or just a minor one (5.10.0 -> 5.10.1). Triggers are not meant for this kind of hand-holding jobs. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
