From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC manager] triggers: add path-based trigger interest
Date: Tue, 5 Nov 2024 12:43:38 +0100 [thread overview]
Message-ID: <20241105114338.473274-1-f.gruenbichler@proxmox.com> (raw)
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
reply other threads:[~2024-11-05 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241105114338.473274-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox