Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gemify rake #862

Closed
wants to merge 4 commits into from
Closed

Gemify rake #862

wants to merge 4 commits into from

Conversation

voxik
Copy link
Contributor

@voxik voxik commented Apr 2, 2015

No description provided.

@drbrain
Copy link
Member

drbrain commented Apr 2, 2015

I approve of this change.

Some test expects some gems to be available on $LOAD_PATH. For example,
RubyGem's test suite requires Rake.

This is currently rather naive implementation, since we don't have
RubyGems at hand to use something like
Gem::Specification#add_self_to_load_path.
@voxik
Copy link
Contributor Author

voxik commented Apr 3, 2015

Now I noticed that some RubyGems were failing due to missing Rake, so the 7d2b6a8 commit add bundled gems on $LOAD_PATH (although the approach is rather naive ATM, but it can be improved later if needed).

@hsbt hsbt self-assigned this Apr 3, 2015
@voxik
Copy link
Contributor Author

voxik commented Apr 3, 2015

Weird, why it fails on travis? The gems are not expanded there for some reason?

@hsbt
Copy link
Member

hsbt commented Apr 4, 2015

@voxik Travis instance is fragile environment :(

@hsbt hsbt closed this in c4ee0df Apr 4, 2015
@voxik voxik deleted the gemify-rake branch April 4, 2015 20:45
mmasaki pushed a commit to mmasaki/ruby that referenced this pull request May 30, 2015
* test/rake/*: ditto.
* tool/rbinstall.rb: ditto.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50163 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants