← Back to issue list

Include appropriate craft-parts environment variables when packing with `--shell`, `--debug`, etc.

View original Github issue

Metadata

Project
craft-application
Number
#435
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to set craft-parts environment variables such as CRAFT_STAGE when launching a shell via --shell or --debug, so override scripts can be tested faster. Unlabelled and without comments.

Suggested action: needs triage

Reason: The issue has no labels, assignee, or comments, so it has not been categorised or prioritised. Code inspection confirms _launch_shell() runs plain bash without injecting craft-parts environment variables, while craft-parts generates CRAFT_STAGE and related variables in _get_global_environment(), so the request is valid and scoped but still needs triage.

Evaluated by: mr-cal-bot

Impact: 35 Quick Win: 8 Complexity: 60 Confidence: 65 Actionability: 60

Issue body

### What needs to get done Include the relevant environment variables set by craft-parts when using `--debug` or `--shell` on a lifecycle command. ### Why it needs to get done testing out override scripts with variables like `$CRAFT_STAGE` already set would make debugging much faster.

Evaluation history

Date Model Scores Action Summary
~deepseek/deepseek-pro-latest
Impact: 35
Quick Win: 8
Complexity: 60
Confidence: 65
Actionability: 60
needs triage Feature request to set craft-parts environment variables such as CRAFT_STAGE when launching a shell via --shell or --debug, so override scripts can be tested faster. Unlabelled and without comments.
stealth/space-bunny-alpha
Impact: 50
Quick Win: 18
Complexity: 52
Confidence: 88
Actionability: 76
needs triage Add craft-parts lifecycle variables such as CRAFT_STAGE to shells launched by --shell and --debug; current shells still start plain bash and the request lacks triage.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 22
Complexity: 20
Confidence: 75
Actionability: 70
keep open Feature request to include CRAFT_* environment variables (like CRAFT_STAGE) in interactive debug shells (--debug, --shell, --shell-after) for easier debugging of override scripts.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18
Staleness: 70
Complexity: 40
Confidence: 75
Support Request: 10
needs triage Feature request to expose craft-parts environment variables (e.g. $CRAFT_STAGE) in the shell launched by --shell/--debug on lifecycle commands like pack, to speed up override-script debugging. Open, unlabelled, zero comments, no activity since ~465 days ago.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 25
Confidence: 80
Support Request: 10
needs triage Feature request to expose craft-parts environment variables in debug and shell modes for lifecycle commands. Unlabelled, zero comments, and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Feature request to expose craft-parts environment variables during --shell or --debug sessions to speed up debugging override scripts. Currently unlabelled and unassessed by maintainers.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#436 feat: support shell/shell-after and debug in 'pack' craft-application merged Merged craft-application#436 (commit ab55ec81), adding --shell/--shell-after to pack and making --debug shell into the build environment when packing fails; fixes #430.
70%