Make sure you're NOT using system ruby, instead use a version of ruby from rvm
,
rbenv
, or chruby
.
If you're not sure, run the following command and check that the output is NOT /usr/bin/ruby
:
$ which ruby
/usr/bin/ruby ## System Ruby
Longer answer: It is difficult to test against all versions of system ruby which change in each macOS release.
System Ruby belongs to the operating system and can change at any time, and can't always be removed or repaired.
Installing Ruby with a version manager places ruby and gems under one's home directory. It also allows for a single
tested, known-working version of Ruby to run the application against.
This project's supported Ruby version can be found in the .ruby-version
file. The supported version of rubygems
gem can be found in the .rubygems-version
file. The currently supported set of Gems can be found in the
Gemfile.lock
.
Why do my edits keep getting reverted? I change the recipe, but every time I run soloist it's changed back
You're editing the recipe under sprout-wrap/cookbooks
. That is a directory that is checked-out from the sources
(as defined in Cheffile
) every chef run—overwriting your changes.
Make your changes under sprout-wrap/site-cookbooks
instead; those changes won't be overwritten.
Why does sprout-wrap install an older version of RubyMine even though sprout's RubyMine recipe specifies a newer one?
You need to update the git SHAs specified in sprout-wrap's Cheffile.lock
.
Run the following command in the root of your copy of the sprout-wrap repo:
librarian-chef update
There are primarily 2 reasons that we install XCode in sprout-wrap:
- System Ruby on OS X >= Mountain Lion uses
xcrun
to detectcc
.xcrun
is not designed to work with the standalone Command Line Tools. - sprout-wrap is used to build workstations for iOS development. Having XCode available is handy in this situation.