You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given a project which uses RVM and has its own RVM gemset
when I install sepa_king v0.11.1 using bundle install,
then a binstub called rake(!) is created
thereby overwriting the binstub created by the rake gem itself.
The erroneously created binstub:
#!/usr/bin/env ruby_executable_hooks## This file was generated by RubyGems.## The application 'sepa_king' is installed as part of a gem, and# this file is here to facilitate running it.#require'rubygems'version=">= 0.a"ifARGV.firststr=ARGV.firststr=str.dup.force_encoding("BINARY")ifstr.respond_to?:force_encodingifstr =~ /\A_(.*)_\z/andGem::Version.correct?($1)thenversion= $1
ARGV.shiftendendifGem.respond_to?(:activate_bin_path)loadGem.activate_bin_path('sepa_king','rake',version)elsegem"sepa_king",versionloadGem.bin_path("sepa_king","rake",version)end
loads sepa_king/bin/rake which then loads rake/exe/rake
but the gem repository paths are not managed correctly,
resulting in error messages like
$ rake -T
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Could not find gem 'rspec'in any of the gem sources listed in your Gemfile.
Run `bundle install` to install missing gems.
even though bundle install will show that rspec was installed all along.
The text was updated successfully, but these errors were encountered:
The binstub bin/rake was accidentally added in
salesking@7cdb97b
and is prone to break projects using rake.
This commit removes the binstub as well as the executables file list
from the gemspec to prevent unintended additions of executables
in future commits.
Given a project which uses RVM and has its own RVM gemset
when I install
sepa_king
v0.11.1 usingbundle install
,then a binstub called
rake
(!) is createdthereby overwriting the binstub created by the
rake
gem itself.The erroneously created binstub:
loads
sepa_king/bin/rake
which then loadsrake/exe/rake
but the gem repository paths are not managed correctly,
resulting in error messages like
even though
bundle install
will show thatrspec
was installed all along.The text was updated successfully, but these errors were encountered: