bfd42a1914
Newly generated binstubs will check for the string `This file was generated by Bundler` inside `bin/bundle`, so we'd have to update that anyway. Also, there is a non-zero chance the updated `bundle` binstub resolves some of the setup-specific issues we've seen.
27 lines
747 B
Ruby
Executable file
27 lines
747 B
Ruby
Executable file
#!/usr/bin/env ruby
|
|
# frozen_string_literal: true
|
|
|
|
#
|
|
# This file was generated by Bundler.
|
|
#
|
|
# The application 'cucumber' is installed as part of a gem, and
|
|
# this file is here to facilitate running it.
|
|
#
|
|
|
|
ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
|
|
|
|
bundle_binstub = File.expand_path("bundle", __dir__)
|
|
|
|
if File.file?(bundle_binstub)
|
|
if File.read(bundle_binstub, 300) =~ /This file was generated by Bundler/
|
|
load(bundle_binstub)
|
|
else
|
|
abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
|
|
Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
|
|
end
|
|
end
|
|
|
|
require "rubygems"
|
|
require "bundler/setup"
|
|
|
|
load Gem.bin_path("cucumber", "cucumber")
|