vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
GIT
|
2018-05-23 09:14:18 +02:00
|
|
|
remote: https://github.com/hashicorp/vagrant-spec.git
|
|
|
|
|
revision: 9413ab298407114528766efefd1fb1ff24589636
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
specs:
|
|
|
|
|
vagrant-spec (0.0.1)
|
|
|
|
|
childprocess (~> 0.6.0)
|
|
|
|
|
log4r (~> 1.1.9)
|
|
|
|
|
rspec (~> 3.5.0)
|
|
|
|
|
thor (~> 0.18.1)
|
|
|
|
|
|
|
|
|
|
PATH
|
|
|
|
|
remote: .
|
|
|
|
|
specs:
|
2018-05-23 09:14:18 +02:00
|
|
|
vagrant (2.1.1)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
childprocess (~> 0.6.0)
|
|
|
|
|
erubis (~> 2.7.0)
|
2018-03-04 08:28:45 +01:00
|
|
|
hashicorp-checkpoint (~> 0.1.5)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
i18n (>= 0.6.0, <= 0.8.0)
|
|
|
|
|
listen (~> 3.1.5)
|
|
|
|
|
log4r (~> 1.1.9, < 1.1.11)
|
|
|
|
|
net-scp (~> 1.2.0)
|
|
|
|
|
net-sftp (~> 2.1)
|
2018-03-04 08:28:45 +01:00
|
|
|
net-ssh (~> 4.2.0)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
rb-kqueue (~> 0.2.0)
|
|
|
|
|
rest-client (>= 1.6.0, < 3.0)
|
|
|
|
|
ruby_dep (<= 1.3.1)
|
|
|
|
|
wdm (~> 0.1.0)
|
2018-05-23 09:14:18 +02:00
|
|
|
win32-file (~> 0.8.1)
|
|
|
|
|
win32-file-security (~> 1.0.10)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
winrm (~> 2.1)
|
|
|
|
|
winrm-elevated (~> 1.1)
|
|
|
|
|
winrm-fs (~> 1.0)
|
|
|
|
|
|
|
|
|
|
GEM
|
|
|
|
|
remote: https://rubygems.org/
|
|
|
|
|
specs:
|
|
|
|
|
addressable (2.5.2)
|
|
|
|
|
public_suffix (>= 2.0.2, < 4.0)
|
|
|
|
|
builder (3.2.3)
|
|
|
|
|
childprocess (0.6.3)
|
|
|
|
|
ffi (~> 1.0, >= 1.0.11)
|
|
|
|
|
crack (0.4.3)
|
|
|
|
|
safe_yaml (~> 1.0.0)
|
|
|
|
|
diff-lcs (1.3)
|
2018-05-23 09:14:18 +02:00
|
|
|
domain_name (0.5.20180417)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
unf (>= 0.0.5, < 1.0.0)
|
|
|
|
|
erubis (2.7.0)
|
|
|
|
|
fake_ftp (0.1.1)
|
2018-05-23 09:14:18 +02:00
|
|
|
ffi (1.9.23)
|
|
|
|
|
ffi-win32-extensions (1.0.3)
|
|
|
|
|
ffi
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
gssapi (1.2.0)
|
|
|
|
|
ffi (>= 1.0.1)
|
|
|
|
|
gyoku (1.3.1)
|
|
|
|
|
builder (>= 2.1.2)
|
|
|
|
|
hashdiff (0.3.7)
|
2018-03-04 08:28:45 +01:00
|
|
|
hashicorp-checkpoint (0.1.5)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
http-cookie (1.0.3)
|
|
|
|
|
domain_name (~> 0.5)
|
|
|
|
|
httpclient (2.8.3)
|
|
|
|
|
i18n (0.8.0)
|
|
|
|
|
listen (3.1.5)
|
|
|
|
|
rb-fsevent (~> 0.9, >= 0.9.4)
|
|
|
|
|
rb-inotify (~> 0.9, >= 0.9.7)
|
|
|
|
|
ruby_dep (~> 1.2)
|
|
|
|
|
little-plugger (1.1.4)
|
|
|
|
|
log4r (1.1.10)
|
|
|
|
|
logging (2.2.2)
|
|
|
|
|
little-plugger (~> 1.1)
|
|
|
|
|
multi_json (~> 1.10)
|
|
|
|
|
mime-types (3.1)
|
|
|
|
|
mime-types-data (~> 3.2015)
|
|
|
|
|
mime-types-data (3.2016.0521)
|
2018-03-04 08:28:45 +01:00
|
|
|
multi_json (1.13.1)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
net-scp (1.2.1)
|
|
|
|
|
net-ssh (>= 2.6.5)
|
|
|
|
|
net-sftp (2.1.2)
|
|
|
|
|
net-ssh (>= 2.6.5)
|
2018-03-04 08:28:45 +01:00
|
|
|
net-ssh (4.2.0)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
netrc (0.11.0)
|
|
|
|
|
nori (2.6.0)
|
|
|
|
|
public_suffix (3.0.1)
|
|
|
|
|
rake (12.0.0)
|
2018-03-04 08:28:45 +01:00
|
|
|
rb-fsevent (0.10.3)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
rb-inotify (0.9.10)
|
|
|
|
|
ffi (>= 0.5.0, < 2)
|
|
|
|
|
rb-kqueue (0.2.5)
|
|
|
|
|
ffi (>= 0.5.0)
|
|
|
|
|
rest-client (2.0.2)
|
|
|
|
|
http-cookie (>= 1.0.2, < 2.0)
|
|
|
|
|
mime-types (>= 1.16, < 4.0)
|
|
|
|
|
netrc (~> 0.8)
|
|
|
|
|
rspec (3.5.0)
|
|
|
|
|
rspec-core (~> 3.5.0)
|
|
|
|
|
rspec-expectations (~> 3.5.0)
|
|
|
|
|
rspec-mocks (~> 3.5.0)
|
|
|
|
|
rspec-core (3.5.4)
|
|
|
|
|
rspec-support (~> 3.5.0)
|
|
|
|
|
rspec-expectations (3.5.0)
|
|
|
|
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
|
|
|
rspec-support (~> 3.5.0)
|
|
|
|
|
rspec-its (1.2.0)
|
|
|
|
|
rspec-core (>= 3.0.0)
|
|
|
|
|
rspec-expectations (>= 3.0.0)
|
|
|
|
|
rspec-mocks (3.5.0)
|
|
|
|
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
|
|
|
rspec-support (~> 3.5.0)
|
|
|
|
|
rspec-support (3.5.0)
|
|
|
|
|
ruby_dep (1.3.1)
|
|
|
|
|
rubyntlm (0.6.2)
|
|
|
|
|
rubyzip (1.2.1)
|
|
|
|
|
safe_yaml (1.0.4)
|
|
|
|
|
thor (0.18.1)
|
|
|
|
|
unf (0.1.4)
|
|
|
|
|
unf_ext
|
2018-03-04 08:28:45 +01:00
|
|
|
unf_ext (0.0.7.5)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
wdm (0.1.1)
|
|
|
|
|
webmock (2.3.2)
|
|
|
|
|
addressable (>= 2.3.6)
|
|
|
|
|
crack (>= 0.3.2)
|
|
|
|
|
hashdiff
|
2018-05-23 09:14:18 +02:00
|
|
|
win32-file (0.8.1)
|
|
|
|
|
ffi
|
|
|
|
|
ffi-win32-extensions
|
|
|
|
|
win32-file-stat (>= 1.4.0)
|
|
|
|
|
win32-file-security (1.0.10)
|
|
|
|
|
ffi
|
|
|
|
|
ffi-win32-extensions
|
|
|
|
|
win32-file-stat (1.5.5)
|
|
|
|
|
ffi
|
|
|
|
|
ffi-win32-extensions
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
winrm (2.2.3)
|
|
|
|
|
builder (>= 2.1.2)
|
|
|
|
|
erubis (~> 2.7)
|
|
|
|
|
gssapi (~> 1.2)
|
|
|
|
|
gyoku (~> 1.0)
|
|
|
|
|
httpclient (~> 2.2, >= 2.2.0.2)
|
|
|
|
|
logging (>= 1.6.1, < 3.0)
|
|
|
|
|
nori (~> 2.0)
|
|
|
|
|
rubyntlm (~> 0.6.0, >= 0.6.1)
|
|
|
|
|
winrm-elevated (1.1.0)
|
|
|
|
|
winrm (~> 2.0)
|
|
|
|
|
winrm-fs (~> 1.0)
|
2018-03-04 08:28:45 +01:00
|
|
|
winrm-fs (1.2.0)
|
vagrant: Build from source
This is not quite as elegant as using `bundlerApp`,
which I could not get working.
However, this still uses most of the Ruby infrastructure,
including stock bundix, and should be fairly reasonable to maintain.
This means no more hacks to work around wrong embedded binaries,
and no need for an old version of Ruby.
Note that `vagrant share` is no longer included,
as that functionality is closed-source
and not present in the upstream source code.
The Vagrant maintainers publish official Vagrant installers,
which they prefer people use as most platforms don't
have great support for pinning known-good dependencies.
When run outside one of the offical installers,
Vagrant normally prints a warning to that effect.
However, Vagrant does run outside the installer environment
(nominally to support Vagrant development),
and this has the effect of functioning better by respecting
OS certs and shared libraries,
as opposed to trying to use bundled versions.
To keep these postive side effects without having to see the warning
on every Vagrant invocation, patch out the call to print the warning.
Note that I have reset the maintainers since the implementation is
totally redone; I'm happy to re-add any of the current maintainers.
2017-10-30 07:21:07 +01:00
|
|
|
erubis (~> 2.7)
|
|
|
|
|
logging (>= 1.6.1, < 3.0)
|
|
|
|
|
rubyzip (~> 1.1)
|
|
|
|
|
winrm (~> 2.0)
|
|
|
|
|
|
|
|
|
|
PLATFORMS
|
|
|
|
|
ruby
|
|
|
|
|
|
|
|
|
|
DEPENDENCIES
|
|
|
|
|
fake_ftp (~> 0.1.1)
|
|
|
|
|
rake (~> 12.0.0)
|
|
|
|
|
rspec (~> 3.5.0)
|
|
|
|
|
rspec-its (~> 1.2.0)
|
|
|
|
|
vagrant!
|
|
|
|
|
vagrant-spec!
|
|
|
|
|
webmock (~> 2.3.1)
|
|
|
|
|
|
|
|
|
|
BUNDLED WITH
|
|
|
|
|
1.14.6
|