Ability to build a hooks only charm
Metadata
Current evaluation
Closed unmerged; the --bare CLI was superseded by plugin-based building in #458 (9dc20872). Generic hooks-only charm support was later delivered by #596 (0dacae0a).
Resolution: closed superseded
Reason: Maintainers rejected the special CLI option and said the capability would be delivered through the new plugin-based building mechanism in #458, merged as 9dc20872. The underlying limitation in #334 was subsequently fixed by #596, commit 0dacae0a.
Evaluated by: mr-cal-bot
No scores available.
Issue body
A very simple hack on the current charmcraft code to support building hooks only charms, by adding a `--bare/-b` option to `build`/`pack`.
This will prevent `charmcraft` from requiring an `entrypoint`, prevent it from creating `dispatch` when building a bare charm. A `venv` directory will still be created and populated in the charm *if* there is a `requirements.txt` file
Fixes #334
Related #329
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed unmerged; the --bare CLI was superseded by plugin-based building in #458 (9dc20872). Generic hooks-only charm support was later delivered by #596 (0dacae0a). | |
| stealth/space-bunny-alpha | — | closed superseded | Closed unmerged: maintainers rejected the --bare CLI approach in favor of plugin-based builds, delivered in canonical/charmcraft#458 (merge 9dc20872). | |
| stealth/space-bunny-alpha | — | closed superseded | PR #335 was closed unmerged after maintainers rejected the --bare CLI hack. Hooks-only build support was deferred to the upcoming plugin-based build mechanism and later landed through PR #596. | |
| stealth/space-bunny-alpha | — | closed superseded | Unmerged --bare option superseded by the plugin-based build mechanism; maintainer said it would be addressed through the new mechanism. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging. Maintainers declined the CLI flag approach, deciding to implement hooks-only charm support via a new plugin-based build system instead. The request was superseded by the planned architecture update. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. Maintainers opted to implement hooks-only charm support via a new parts/plugins building mechanism instead of the proposed CLI flag, superseding this PR. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#596
(confidence 99%)
Fixed the underlying generic hooks-only charm build limitation tracked by #334.
-
Superseded By:
canonical/charmcraft#458
(confidence 98%)
Introduced the plugin-based building approach preferred by maintainers instead of the --bare flag.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #334 Charmcraft cannot build a non-operator framework charm | charmcraft | closed | Generic hooks-only charm packing was fixed by PR #596, merged as 0dacae0a, allowing builds without an Operator Framework entry point; the fix shipped in edge. | |
| #329 charmcraft upload of "bash"/"hooks only" charm doesn't work | charmcraft | closed | Legacy hooks-only charms were unsupported; maintainers directed users to charm push, and the report closed without a code fix. |