vagrant-lxc-ng/Gemfile

source 'https://rubygems.org'

group :development do
  gem 'vagrant', git: 'https://github.com/mitchellh/vagrant.git', branch: 'main'
  gem 'guard'
  gem 'guard-rspec'
  gem 'rb-inotify'
end

group :development, :test do
  gem 'rake', '~> 10.4.2'
  gem 'rspec', '~> 3.5.0'
  gem 'coveralls', '~> 0.7.2', require: (ENV['COVERAGE'] == 'true')
  gem 'vagrant-spec', git: 'https://github.com/mitchellh/vagrant-spec.git', branch: 'main'
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
Not so initial commit 2013-02-25 04:58:04 +00:00			`source 'https://rubygems.org'`

Remove vendored vagrant code and gem dependencies 2013-03-14 22:44:39 +00:00			`group :development do`
fix: gem vagrant* (dependencies) now use branch 'main' instead of 'master' 2021-05-04 19:26:52 +00:00			`gem 'vagrant', git: 'https://github.com/mitchellh/vagrant.git', branch: 'main'`
Remove vendored vagrant code and gem dependencies 2013-03-14 22:44:39 +00:00			`gem 'guard'`
			`gem 'guard-rspec'`
			`gem 'rb-inotify'`
			`end`
Check-in some TODOs and REFACTORs that have been around for a while 2013-03-04 04:16:45 +00:00
Remove vendored vagrant code and gem dependencies 2013-03-14 22:44:39 +00:00			`group :development, :test do`
Remove Gemfile.lock and properly lock stuff in Gemfile 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`. 2017-12-13 20:33:05 +00:00			`gem 'rake', '~> 10.4.2'`
Bump minimum requirements for next vagrant-lxc release (v1.5) We now depend on vagrant 1.9+ and LXC 2.0+, following bundled version in debian stretch. Also, update Gemfile to target latest vagrant/vagrant-spec. It's too complicated to test against old vagrant versions. Vagrant 1.8.x didn't specify an upper bound for supported versions but vagrant 1.9 does (<2.4). This breaks out CI testing matrix which tests against 2.3, 2.4 and 2.5. So let's make our live easier and just test against the latest vagrant version and try not to mistakenly drop support for our lowest supported vagrant version... 2018-07-24 13:37:34 +00:00			`gem 'rspec', '~> 3.5.0'`
Remove Gemfile.lock and properly lock stuff in Gemfile 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`. 2017-12-13 20:33:05 +00:00			`gem 'coveralls', '~> 0.7.2', require: (ENV['COVERAGE'] == 'true')`
fix: gem vagrant* (dependencies) now use branch 'main' instead of 'master' 2021-05-04 19:26:52 +00:00			`gem 'vagrant-spec', git: 'https://github.com/mitchellh/vagrant-spec.git', branch: 'main'`
core: Group vagrant plugins under the :plugins group on Vagrantfile This is required so that vagrant 1.5 picks them up 2014-03-11 19:37:29 +00:00			`end`

			`group :plugins do`
Minor tweaks to accomodate acceptance specs 2014-03-13 01:15:58 +00:00			`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`
Update gemfile 2014-04-04 19:27:00 +00:00			`gemspec`
Remove vendored vagrant code and gem dependencies 2013-03-14 22:44:39 +00:00			`end`