← Back to issue list

Ruby plugin paths are inconsistent

View original Github issue

Metadata

Project
craft-parts
Number
#1413
Type
issue
State
closed
Author
steinbro
Labels
Status: Triaged
Created
Updated
Closed

Current evaluation

Fixed by merged PR #1414 (commit df9bfb48), standardizing Ruby interpreter, gem, bundle, and executable paths so gem and bundle installs use the system gem path.

Resolution: closed resolved

Reason: Merged PR #1414 resolves #1413 and landed as commit df9bfb48, aligning gem and bundle installation with the Ruby plugin's system gem path.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### Bug Description The Ruby plugin as implemented in #1395 treats paths inconsistently: 1. The install prefix for the interpreter is `$CRAFT_PART_INSTALL/usr`. 2. `GEM_HOME` is `$CRAFT_PART_INSTALL`. 3. `BUNDLE_PATH` is `$CRAFT_PART_INSTALL`. This means: 1. The ruby executable is in `/usr/bin/`, and system-global gems are in ``/usr/lib/ruby/gems/3.2.0/`. 2. Gem-installed executables are in `/bin` 3. Bundle-installed executables are in `/ruby/<ruby_version>/bin` Instead, we should set the build environment so that `gem install` and `bundle install` go into the system gem path. ### To Reproduce N/A ### part yaml ```shell ``` ### Relevant log output ```shell N/A ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #1414 (commit df9bfb48), standardizing Ruby interpreter, gem, bundle, and executable paths so gem and bundle installs use the system gem path.
stealth/space-bunny-alpha — closed resolved Fixed inconsistent Ruby plugin paths in merged PR #1414 (commit df9bfb48), aligning gem and bundle installations with the system gem path.
qwen/qwen3.6-35b-a3b — — Closed without resolution. An internal Jira ticket (CRAFT-4950) was created to track the inconsistent Ruby plugin paths. No fix or pull request was merged.
qwen/qwen3.6-35b-a3b — — The issue was closed and synced to Jira ticket CRAFT-4950. No fix or resolution was documented in GitHub, indicating it was tracked externally without a resolved outcome here.
qwen/qwen3.6-35b-a3b — — Abandoned without resolution. Ruby plugin path inconsistency remains unfixed, with tracking moved to internal Jira ticket CRAFT-4950.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. Only an automated Jira sync comment was posted, indicating the report was logged internally but received no follow-up.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/craft-parts#1414 (confidence 100%)

    Merged fix standardizing the Ruby plugin's interpreter, gem, bundle, and executable paths.

  • Caused By: canonical/craft-parts#1395 (confidence 99%)

    The original Ruby plugin implementation introduced the inconsistent path environment.

Related issues

Issue Project State Summary Similarity
#1414 fix: standardize paths in ruby plugin craft-parts merged Merged PR #1414 in commit df9bfb48, standardizing Ruby plugin paths and fixing #1413, with reviewer-requested RUBYLIB and test compatibility corrections.
80%
#1730 ruby plugin: be smarter about arch-specific paths snapcraft merged Ruby plugin architecture-path handling was fixed by replacing hard-coded amd64/i386 paths with glob-based detection; PR #1730 merged as commit befa5c307.
71%