[WIP] charmcraft config: introduce support for bases keyword
Metadata
Current evaluation
Abandoned WIP; bases support landed separately through merged PRs #339 (9af3b121) and #341 (b76170f9), covering long- and short-form configurations.
Resolution: closed superseded
Reason: Closed as an abandoned WIP after bases support was implemented separately: PR #339 merged via 9af3b121 with implementation 79cd72ca, and PR #341 merged via b76170f9 with implementation f858beaa.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- Support short-form syntax where a base without 'build-on'
or 'run-on' implies build_on=base coupled with run_on=base.
- Support long-form syntax where explicit build-on and run-on
lists are used to support any configuration combination.
- Support combined lists, where a short-form base item will
be expanded into the long-form equivalent.
Note that this does not include unit testing for errors. There
is a fair bit of other work to be done to improve error handling.
Note that this does not automatically set any implied architecture
in the Config, though an empty list of architectures would imply
the default (host's) is to be used.
Signed-off-by: Chris Patterson <chris.patterson@canonical.com>
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Abandoned WIP; bases support landed separately through merged PRs #339 (9af3b121) and #341 (b76170f9), covering long- and short-form configurations. | |
| stealth/space-bunny-alpha | — | closed superseded | Abandoned WPR; bases support landed separately through merged PRs #339 and #341, adding long- and short-form configurations. | |
| qwen/qwen3.6-35b-a3b | — | — | Charmcraft bases keyword support was closed without merging. The branch was abandoned with twelve unresolved review comments and pending unit tests, leaving the feature unimplemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. The change added short, long, and combined syntax for the charmcraft bases keyword but remained a work in progress. Lack of unit tests and error handling resulted in abandonment. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/charmcraft#339
(confidence 99%)
Merged long-form bases support, replacing the corresponding WIP work in #299.
-
Superseded By:
canonical/charmcraft#341
(confidence 99%)
Merged short-form bases support, expanding a base into matching build-on and run-on entries.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #383 commands/build: charm file name format support for bases (CRAFT-66) | charmcraft | merged | Merged PR #383 (commit 951f6aaa; merge 1c839909) added bases-aware charm filename formatting and tests, retaining the legacy runtime path pending default-bases configuration. | |
| #399 Implement support for Bases in Store layer (CRAFT-298) | charmcraft | merged | Merged Bases support in Charmcraft's Store layer for use by status; PR #399 landed via 5c49339b (implementation 3c3e4c2a). | |
| #339 config: introduce long-form bases support | charmcraft | merged | Merged PR #339 via 9af3b121 (implementation 79cd72ca), adding long-form bases configuration; short-form support was deferred. | |
| #341 config: add short-form bases support (CRAFT-11) | charmcraft | merged | Merged #341, adding short-form base support so a base string expands to matching build-on and run-on entries. | |
| #411 build: pack charm in provided environment when using bases (CRAFT-313) | charmcraft | merged | Merged PR #411 (CRAFT-313) to pack each viable bases configuration in its provided build environment; merge commit 523c6fb0. | |
| #479 The control of `bases` in `charmcraft.yaml` should be different for bundles | charmcraft | closed | Fixed by merged PR #545: bundles no longer warn when bases is omitted, and bundle configurations declaring bases are rejected. | |
| #73 Add multi-bases support for charm build plans | craft-platforms | closed | Multi-base charm build-plan support was merged in PR #81 (commit 519b705), with validation tightening and error-handling updates; it resolved #73. |