snapcraft options are position-dependent
Metadata
Current evaluation
Request to make --use-lxd position-independent or reject it before a lifecycle command; still open and untriaged, while current code attaches --use-lxd to lifecycle command parsers.
Suggested action: needs triage
Reason: The body provides an exact comparison of `snapcraft --use-lxd build` and `snapcraft build --use-lxd`, and @~jgneff confirms it blocks a simple Bash alias. There are no labels or maintainer responses; current cli.py uses a default PackCommand while core22 lifecycle.py registers --use-lxd on individual lifecycle parsers, so current behavior needs verification before deciding where global parsing should be fixed.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
11
Complexity:
52
Confidence:
79
Actionability:
62
Issue body
$ snapcraft --use-lxd build
Support for 'multipass' needs to be set up. Would you like to do that it now? [y/N]:
vs.
$ snapcraft build --use-lxd
Launching a container
Command line options being positional makes for a very confusing user experience. And if `--use-lxd` is an invalid option before the command, it should be a straight-up error instead of being ignored.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
11
Complexity:
52
Confidence:
79
Actionability:
62
|
needs triage | Request to make --use-lxd position-independent or reject it before a lifecycle command; still open and untriaged, while current code attaches --use-lxd to lifecycle command parsers. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
16
Complexity:
52
Confidence:
82
Actionability:
85
|
needs triage | LXD selection is tied to command position: snapcraft --use-lxd build differs from snapcraft build --use-lxd; the exact behavior and alias workaround are documented, but no current fix or maintainer triage is recorded. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
11
Complexity:
60
Confidence:
75
Actionability:
70
|
needs triage | snapcraft --use-lxd option must be placed after the subcommand; before it is silently ignored, causing confusing behavior. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
10
Staleness:
95
Complexity:
30
Confidence:
65
Support Request:
10
|
close stale | Reports snapcraft CLI flags are position-dependent: `snapcraft --use-lxd build` silently ignores the flag while `snapcraft build --use-lxd` works. Unanswered for ~7 years; `--use-lxd` was later removed from snapcraft, making the example obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
10
|
needs triage | Unlabelled report that snapcraft CLI flags behave differently depending on whether they precede or follow the subcommand. No maintainer response or comments in nearly seven years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | CLI options in snapcraft are position-dependent, causing confusing behavior and silent failures when flags precede subcommands. The issue is extremely stale with no maintainer engagement or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
35
Confidence:
75
Support Request:
10
|
close stale | Reports confusing CLI behavior where snapcraft options must follow the subcommand. Options placed before it trigger unintended prompts or are ignored. No maintainer response or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.