[PVE-User] "Processing triggers for pve-manager" after installing unrelated packages

[Flavio Stanchina]

Dietmar Maurer wrote:
>> pve-manager registers the entire /usr/share/perl5 directory as a trigger. Isn't
>> it a bit too broad
>
> What do you suggest instead?

Looking at the PVE packages, I'd think that a trigger on 
/usr/share/perl5/PVE would be enough. Surely you're using Perl modules 
from other packages, for example I see Apache2::Const being used by 
pve-manager, but what are the chances that an upgrade to such packages 
introduced changes that would require a restart? Especially on Debian 
stable? Common wisdom is to let applications run with old versions of 
libraries until the admin is comfortable restarting services, to prevent 
downtime.

I'll admit I didn't research how this dpkg triggers stuff works until 
now, so feel free to bash me if I'm missing obvious reasons why it needs 
to be as it is.

-- 
Flavio Stanchina
Informatica e Servizi
Trento - Italy