|
6 | 6 | root="$(cd "$(dirname "$0")/.." && pwd)" |
7 | 7 |
|
8 | 8 | env BUNDLE_GEMFILE="$root/Gemfile" bundle install |
9 | | -for gemfile in $root/packages/npm-packages/*/Gemfile; do |
10 | | - # Skip ruby-head-wasm-wasi's Gemfile because it does not need to be installed here |
11 | | - if [[ "$gemfile" == *"/ruby-head-wasm-wasi/Gemfile" ]]; then |
12 | | - continue |
13 | | - fi |
14 | | - |
15 | | - # FIXME: This is a workaround for the following issue: |
16 | | - # 1. `bundle install` does not support auto-self-upgrade for pre-release bundler versions suffixed with ".dev" |
17 | | - # 2. ruby-head-wasm-wasi's component build depends on 2.6.0.dev, which added --target-rbconfig support |
18 | | - # 3. If the "bundle" command here is earlier than 2.6.0.dev, "bundle install" does *not* self-upgrade to |
19 | | - # the specified pre-release version, and it overwrites the Gemfile.lock with the earlier command version. |
20 | | - # 4. Overwritten Gemfile.lock with the earlier bundler version causes auto-self-downgrade when running |
21 | | - # "bundle install --target-rbconfig" inside "rbwasm build" command, then it fails because the earlier |
22 | | - # bundler version does not support --target-rbconfig. |
23 | | - # |
24 | | - # Thus, we temporarily discard the Gemfile.lock changes here to prevent the auto-self-downgrade issue. |
25 | | - # This workaround should be removed once we drop static Ruby builds from ruby-head-wasm-wasi or |
26 | | - # a stable bundler version is released with --target-rbconfig support. |
27 | | - cp "$gemfile.lock" "$gemfile.lock.orig" |
28 | | - env BUNDLE_GEMFILE="$gemfile" bundle install |
29 | | - mv "$gemfile.lock.orig" "$gemfile.lock" |
30 | | -done |
31 | 9 |
|
32 | 10 | # Build vendored jco if Rust toolchain is available and submodule is checked out |
33 | 11 | if command -v rustc && [ -f vendor/jco/package.json ]; then |
|
0 commit comments