* [pve-devel] [RFC manager] triggers: add path-based trigger interest
@ 2024-11-05 11:43 Fabian Grünbichler
0 siblings, 0 replies; only message in thread
From: Fabian Grünbichler @ 2024-11-05 11:43 UTC (permalink / raw)
To: pve-devel
to avoid the need to mark every package shipping PVE-related perl code as
activating the explicit trigger. the explicit trigger can still be used for
packages that need to reload the API without shipping a perl module
the explicit trigger activation can be dropped in PVE 9.0 in packages that ship
perl code, without a need for versioned dependencies.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Currently, the following packages ship perl modules in /usr/share/perl5/PVE,
but don't activate the explicit trigger:
libpve-apiclient-perl libpve-cluster-perl libpve-notify-perl pve-cluster libpve-u2f-server-perl dab
libpve-cluster-perl is upgraded in lockstep with libpve-cluster-api-perl, which does activate the trigger.
manually tested reinstalling `pve-cluster` with and without this patch, seems to work as expected.
are there other paths that might make sense to "watch"?
debian/triggers | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/triggers b/debian/triggers
index aabe418ef..4e3a2a3d9 100644
--- a/debian/triggers
+++ b/debian/triggers
@@ -1 +1,2 @@
interest-noawait pve-api-updates
+interest-noawait /usr/share/perl5/PVE
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-11-05 11:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-11-05 11:43 [pve-devel] [RFC manager] triggers: add path-based trigger interest Fabian Grünbichler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox