← Back to issue list

Ensure the charm libraries related commands work correctly when command not issued in project's root dir

View original Github issue

Metadata

Project
charmcraft
Number
#1002
Type
issue
State
closed
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

No library-command fix was recorded; later PRs #1565/#1592 (commit 06c485fc) restricted --project-dir to init and pack.

Resolution: closed stale

Reason: The issue has no comments, closing reference, or recorded implementation. Commit 06c485fc later restricted --project-dir to init and pack, providing no evidence that fetch/publish library support was delivered.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Most of the current charm libraries infrastructure depend on being standing in the root directory of the project, as the "lib" directory has a specific structure that is validated or used to detect libraries. We need to ensure that all commands for charm libraries (fetch, publish, etc.) work correctly when standing somewhere else and `--project-dir` being used.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale No library-command fix was recorded; later PRs #1565/#1592 (commit 06c485fc) restricted --project-dir to init and pack.
stealth/space-bunny-alpha — closed stale Closed without a recorded fix; history does not confirm that Charmhub library commands gained support for --project-dir outside the project root.
stealth/space-bunny-alpha — closed stale Closed without a recorded resolution; available history does not confirm that fetch/publish gained support for --project-dir outside the project root.
stealth/space-bunny-alpha — closed resolved Project-directory handling was fixed in PR #508, merged as dbad275a, enabling library commands to use --project-dir outside the project root.
qwen3.6-35b-a3b-mtp-q6 — — Closed without comments or linked pull requests. The feature to run charm library commands outside the project root via --project-dir was not implemented, indicating the issue was abandoned.
qwen/qwen3.6-35b-a3b — — Abandoned due to prolonged inactivity and zero comments. The request to make charm library commands work outside the project root directory using --project-dir was closed without implementation or resolution.
qwen3.6-35b-a3b-mtp-q6 — — The request to make charm library commands work outside the project root via --project-dir was closed and abandoned without comments or implementation details due to prolonged inactivity.

Update history

No update history recorded yet.

Related work

  • Superseded By: canonical/charmcraft#1565 (confidence 90%)

    The CLI change limited --project-dir to init and pack rather than adding it to library commands.

  • Superseded By: canonical/charmcraft#1592 (confidence 85%)

    Associated with commit 06c485fc, which applied the restriction to --project-dir.

Related issues

Issue Project State Summary Similarity
#198 `charmcraft init` would be better off with explicit directory name charmcraft closed Kept directory selection on --project-dir; missing directories are now created by #508 (commit 15d530ae).
72%