← Back to issue list

[Feature] Add support for triggers

View original Github issue

Metadata

Project
debcraft
Number
#148
Type
issue
State
open
Author
hector-cao
Labels
—
Created
Updated
Closed
—

Current evaluation

Request to package developer-supplied Debian trigger files in control metadata; it remains untriaged and depends on open maintainer-script support in #145.

Suggested action: needs triage

Reason: The issue has no labels, comments, or maintainer response, and its body explicitly says it needs #145, which remains open. Generic control-file tests cover trigger filenames, but production evidence only shows commit 040b680/#113 automatically generating an ldconfig trigger, not installing developer-supplied trigger files.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 18 Complexity: 50 Confidence: 91 Actionability: 82

Issue body

Triggers is an advanced feature of the Ubuntu/Debian package management system that allows packages to enable notification between them. One package can say, “when something changes (e.g., files installed in a certain directory), another package should run a specific action.” This is useful for packages to defer certain actions until later, instead of running them immediately during installation or upgrade. Without triggers, many packages would repeatedly run expensive tasks (like updating caches or rebuilding indexes) every time they’re installed. Triggers allow these tasks to be batched and run once, improving performance and consistency. debcraft should allow developers to install the triggers file in the package control metadata. This feature needs #145

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 18
Complexity: 50
Confidence: 91
Actionability: 82
needs triage Request to package developer-supplied Debian trigger files in control metadata; it remains untriaged and depends on open maintainer-script support in #145.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 18
Complexity: 22
Confidence: 82
Actionability: 62
needs triage Feature request to let debcraft install a user-supplied `triggers` control file (e.g. debian/triggers, debian/<pkg>.triggers) into the package control tarball. Untriaged: no labels, comments, or maintainer response in 158 days.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 12
Complexity: 50
Confidence: 70
Actionability: 60
needs triage Feature request to add Debian triggers support in debcraft, dependent on maintainer scripts support (#145). No maintainer response or labels yet.
qwen/qwen3.8-27b
Impact: 50
Quick Win: 30
Staleness: 70
Complexity: 40
Confidence: 75
Support Request: 5
needs triage Feature request to let debcraft install user-provided Debian triggers files into package control metadata. Depends on #145 (maintainer scripts). No maintainer response, unlabelled, inactive 126 days.
qwen/qwen3.6-35b-a3b
Staleness: 60
Complexity: 35
Confidence: 85
Support Request: 10
needs triage Feature request to add Debian/Ubuntu package trigger support to debcraft's control metadata generation. Currently unlabelled, unassigned, and blocked by issue #145 with no maintainer interaction for 85 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 55
Complexity: 50
Confidence: 90
Support Request: 10
needs triage Feature request to add Debian/Ubuntu package trigger support to debcraft. Currently unlabelled, has no maintainer comments or activity since creation, and depends on issue #145.

Update history

No update history recorded yet.

Related work

  • Blocked By: canonical/debcraft#145 (confidence 100%)

    The issue explicitly depends on maintainer-script support, and #145 is still open and untriaged.

  • Related To: canonical/debcraft#113 (confidence 88%)

    Commit 040b680 added automatic ldconfig trigger generation for shared libraries, but does not demonstrate support for project-provided triggers files.

Related issues

No related issues found above the similarity threshold.