← Back to issue list

Document how `stage-packages` differs from installing a package on the system

View original Github issue

Metadata

Project
charmcraft
Number
#1992
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Documentation is still needed to distinguish build-time stage-packages from runtime apt installation; prerequisites #1839 and #1844 remain open, and current docs lack dedicated guidance.

Suggested action: needs triage

Reason: The body explicitly makes fully implemented staged-package support from #1839 and #1844 a prerequisite; both remain open, and repository search found examples but no explanation or apt operator-library guidance. The issue has no labels, and its sole recent comment is an automated Jira synchronization rather than maintainer triage.

Evaluated by: mr-cal-bot

Impact: 42 Quick Win: 14 Complexity: 41 Confidence: 92 Actionability: 57

Issue body

### What needs to get done Once staged packages are fully implemented (#1839, #1844), write documentation to explain how staging a package differs from installing it in the resulting system and how to use [operator libs](https://charmhub.io/operator-libs-linux/libraries/apt) to achieve this instead. ### Why it needs to get done Users who use other crafts are likely to expect `stage-packages` to work the same way in charmcraft. However, because of how fundamentally different charms are from snaps and rocks, they won't. See #1990 for an example.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 42
Quick Win: 14
Complexity: 41
Confidence: 92
Actionability: 57
needs triage Documentation is still needed to distinguish build-time stage-packages from runtime apt installation; prerequisites #1839 and #1844 remain open, and current docs lack dedicated guidance.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 16
Complexity: 10
Confidence: 80
Actionability: 60
needs triage Documentation task to explain how stage-packages differs from system package installation, blocked by implementation issues #1839 and #1844 which remain open
qwen/qwen3.8-27b
Impact: 35
Quick Win: 24
Staleness: 65
Complexity: 30
Confidence: 78
Support Request: 0
keep open Documentation task to explain how stage-packages differs from system package installation in charms and how to use operator libs instead. Blocked on stage-packages implementation (#1839, #1844), still open; no activity for over a year.
qwen/qwen3.6-35b-a3b
Staleness: 75
Complexity: 15
Confidence: 85
Support Request: 5
needs triage Documentation task requesting clarification on how stage-packages differs from system installation in charmcraft. Currently unlabelled and inactive since an auto-bot message ~340 days ago.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 15
Confidence: 80
Support Request: 5
needs triage Documentation task explaining stage-packages differences from system installation and operator lib usage. Unlabelled, unassigned, and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 10
Confidence: 75
Support Request: 5
needs triage Documentation task to explain stage-packages differences from system installation and how to use operator libs instead. Unlabelled and awaiting maintainer assessment after over a year of inactivity.

Update history

No update history recorded yet.

Related work

  • Related To: charmcraft#1990 (confidence 100%)

    The body cites #1990 as an example of users expecting cross-tool stage-packages behavior.

  • Blocked By: charmcraft#1839 (confidence 98%)

    The issue explicitly identifies clean staging support in #1839 as a prerequisite.

  • Blocked By: charmcraft#1844 (confidence 90%)

    The issue explicitly names #1844 as a prerequisite; it remains open despite merged PR #1875 implementing part of the work.

Related issues

No related issues found above the similarity threshold.