Can snapcraft commands default to base in snapcraft.yaml from build subdirectories?
Metadata
Current evaluation
Feature request to make snapcraft commands use base from snapcraft.yaml when run from subdirectories of the build directory. Untriaged, 4 years old, zero maintainer interaction.
Suggested action: needs triage
Reason: This issue has never been triaged by a maintainer (zero comments, no labels, no assignee) despite being open for 4 years. The feature request is clear and well-scoped, but the extreme age and complete lack of maintainer engagement create uncertainty about current relevance. A maintainer should assess whether this behavior is still the case in the current codebase and whether the feature is worth pursuing.
Impact:
30
Quick Win:
21.0
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
Issue body
I can see that if I'm running commands like "snapcraft plugins", if I happen to be at the top of a snap build directory, then the command will use the base specified in the snapcraft.yaml file.
However, if I'm in some (non-snap/) subdirectory of that build directory, then the command reverts to simply using the latest supported base. Would it be difficult to extend snapcraft's behaviour to act more like Git, in that no matter where you are in a build directory, the base from the snapcraft.yaml file associated with that build directory will be used? That would be more consistent behaviour.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
30
Quick Win:
21.0
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
20
|
needs triage | Feature request to make snapcraft commands use base from snapcraft.yaml when run from subdirectories of the build directory. Untriaged, 4 years old, zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Request to make snapcraft commands automatically detect and use the base from snapcraft.yaml when run from subdirectories, instead of defaulting to the latest supported base. Unanswered and inactive for over four years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Request to make snapcraft commands automatically detect and use the base from snapcraft.yaml when run from subdirectories. Currently inactive for ~4 years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to make snapcraft commands inherit the base from snapcraft.yaml when executed from subdirectories. Currently untriaged, zero comments, and inactive for nearly 4 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Feature request to make snapcraft recursively locate snapcraft.yaml when run from subdirectories. Currently untriaged and inactive for over 3 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2012950 Can "snapcraft extensions" support "--base=" option like plugins? | snapcraft (launchpad) | open | Feature request to add --base option to snapcraft extensions command, mirroring snapcraft plugins. Untriaged, no maintainer engagement. |