fe7d638b35
No other vagrant plugin use `Gemfile.lock`. It doesn't feel right. When removing it, however, we end up with many dependencies conflicts. It then becomes necessary to freeze dependencies in `Gemfile`.
24 lines
798 B
Ruby
24 lines
798 B
Ruby
source 'https://rubygems.org'
|
|
|
|
group :development do
|
|
gem 'vagrant', git: 'https://github.com/mitchellh/vagrant.git', tag: 'v1.7.4'
|
|
gem 'guard'
|
|
gem 'guard-rspec'
|
|
gem 'rb-inotify'
|
|
end
|
|
|
|
group :development, :test do
|
|
gem 'rake', '~> 10.4.2'
|
|
gem 'rspec', '~> 2.99.0'
|
|
gem 'coveralls', '~> 0.7.2', require: (ENV['COVERAGE'] == 'true')
|
|
gem 'vagrant-spec', git: 'https://github.com/mitchellh/vagrant-spec.git', ref: '1df5a3af81cb7cce568b2eac52b8f6822bcb1d8e'
|
|
end
|
|
|
|
group :plugins do
|
|
acceptance = (ENV['ACCEPTANCE'] == 'true')
|
|
gem 'vagrant-cachier', git: 'https://github.com/fgrehm/vagrant-cachier.git', require: !acceptance
|
|
gem 'vagrant-pristine', git: 'https://github.com/fgrehm/vagrant-pristine.git', require: !acceptance
|
|
gem 'vagrant-omnibus', require: !acceptance
|
|
gemspec
|
|
end
|