docs(uv): clarify stage-packages usage
Metadata
Current evaluation
Merged PR #1589 (acfffd36) fixes #1580 by clarifying uv's default venv location and recommending separate parts for unrelated stage-packages.
Resolution: closed resolved
Reason: PR #1589 was merged into the project as commit acfffd36. The change documents that uv creates its virtual environment in $CRAFT_PART_INSTALL and advises using a separate part for unrelated stage-packages, resolving #1580.
Evaluated by: mr-cal-bot
No scores available.
Issue body
## Summary
Clarify that the uv plugin creates the virtual environment in `${CRAFT_PART_INSTALL}` by default, and recommend using a separate part for unrelated `stage-packages`.
Fixes #1580.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #1589 (acfffd36) fixes #1580 by clarifying uv's default venv location and recommending separate parts for unrelated stage-packages. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #1589 via acfffd36, clarifying that uv creates its environment in ${CRAFT_PART_INSTALL} and recommending a separate part for unrelated stage-packages. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged documentation update clarifying uv plugin virtual environment placement and stage-packages usage. Resolves #1580. Approved by two reviewers and force-merged after one OSV security scan check failed. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
20
Complexity:
5
Confidence:
85
|
needs review | Documentation update clarifying uv plugin stage-packages behavior and recommending a separate part. Currently awaiting maintainer review and merge after a recent comment requesting a force-merge to bypass a failing check. |
Update history
| Date | Change |
|---|---|
| updated |
Related work
-
Related To:
craft-parts#1580
(confidence 100%)
The linked documentation issue explicitly states that it was resolved by merged PR #1589.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1580 uv plugin documentation is misleading | craft-parts | closed | Resolved in merged PR #1589 (acfffd36), documenting that uv creates its venv in $CRAFT_PART_INSTALL and advising separate parts for unrelated stage-packages. |