← 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

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.

Suggested action: needs triage

Reason: The issue is a well-scoped feature request from an external contributor with no labels, no maintainer response, and no assignee after 126 days. It explicitly depends on #145 (maintainer scripts), which is itself open and unlabelled, so the feature is blocked on that prerequisite. The generic install_package_control helper already supports arbitrary control file names (tests exercise name="triggers"), so implementation is likely a small dedicated helper, but no maintainer has triaged or prioritized it.

Impact: 50 Quick Win: 30.0 Staleness: 70 Complexity: 40 Confidence: 75 Support Request: 5

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
qwen/qwen3.8-27b
Impact: 50
Quick Win: 30.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 55
Complexity: 40
Confidence: 90
Support Request: 10
needs triage Enable Debian/Ubuntu package trigger support in debcraft to batch deferred actions like cache updates. Open 50 days, zero comments. Blocked on issue #145. Requires triage and assignment.

Update history

No update history recorded yet.

Related work

  • Blocked By: debcraft#145 (confidence 90%)

    Issue body explicitly states 'This feature needs #145' (maintainer scripts support), which is still open and unlabelled.

Related issues

Issue Project State Summary Similarity
#145 [Feature] Add support for maintainer scripts debcraft open Feature request to add support for Debian maintainer scripts (postinst, postrm, prerm, preinst) in debcraft, allowing developers to define script contents and enabling helpers to inject content. No maintainer response or labels yet.
74%
#146 [Feature] Add support for debconf config script debcraft open Feature request for debconf config/templates deployment in debcraft. Triaged (Jira DEBCRAFT-67), and the core functionality has since been implemented via merged installdebconf helper PRs #156 and #162. No activity for about 4 months.
72%