| Port details on branch 2025Q3 |
- vagrant Vagrant Virtual Machine Manager
- 2.4.1_3 sysutils
 =0      2.4.1_2Version of this port present on the latest quarterly branch. - Maintainer: joe@thrallingpenguin.com
- Port Added: 2025-07-24 13:48:27
- Last Update: 2025-08-14 05:20:41
- Commit Hash: 1942d45
- Also Listed In: devel rubygems
- License: MIT
- WWW:
- https://www.vagrantup.com/
- Description:
- Vagrant is a tool for building and distributing virtualized development
environments.
If you want to use vagrant together with an installed gitlab on the same host, use vagrant-gitlab.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - USE_RC_SUBR (Service Scripts)
- no SUBR information found for this port
- Dependency lines:
-
- vagrant>0:sysutils/vagrant
- To install the port:
- cd /usr/ports/sysutils/vagrant/ && make install clean
- To add the package, run one of these commands:
- pkg install sysutils/vagrant
- pkg install vagrant
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: vagrant
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1752906954
SHA256 (hashicorp-vagrant-v2.4.1_GH0.tar.gz) = 19cfa306e3ffae5ddbf30504f61a1a3124aa9a87721b130a14098d4ea1febf89
SIZE (hashicorp-vagrant-v2.4.1_GH0.tar.gz) = 3342333
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- rubygem-builder>=2.1.2 : devel/rubygem-builder
- rubygem-bundler>=1.12.5 : sysutils/rubygem-bundler
- rubygem-main>=1.0 : devel/rubygem-main
- ruby33 : lang/ruby33
- Runtime dependencies:
-
- ca_root_nss>=0 : security/ca_root_nss
- curl : ftp/curl
- rubygem-bcrypt_pbkdf>=1.1 : security/rubygem-bcrypt_pbkdf
- rubygem-childprocess>=4.1.0 : devel/rubygem-childprocess
- rubygem-ed25519>=1.3.0 : security/rubygem-ed25519
- rubygem-erubi>=0 : www/rubygem-erubi
- rubygem-googleapis-common-protos-types>=1.3.0 : devel/rubygem-googleapis-common-protos-types
- rubygem-grpc>=1.56.0 : net/rubygem-grpc
- rubygem-hashicorp-checkpoint>=0.1.5<0.2 : www/rubygem-hashicorp-checkpoint
- rubygem-i18n>=1.12,2<2,2 : devel/rubygem-i18n
- rubygem-ipaddr>=1.2.4 : net/rubygem-ipaddr
- rubygem-listen>=3.7<4 : devel/rubygem-listen
- rubygem-log4r>=1.1.9<1.1.11 : sysutils/rubygem-log4r
- rubygem-mime-types>=3.3 : misc/rubygem-mime-types
- rubygem-net-ftp>=0.2 : ftp/rubygem-net-ftp
- rubygem-net-scp>=4.0.0 : security/rubygem-net-scp
- rubygem-net-sftp>=4.0 : security/rubygem-net-sftp
- rubygem-net-ssh>=7.0.0 : security/rubygem-net-ssh
- rubygem-rb-kqueue>=0.2.0<0.3 : devel/rubygem-rb-kqueue
- rubygem-rexml>=3.2 : textproc/rubygem-rexml
- rubygem-rgl>=0.5.10 : devel/rubygem-rgl
- rubygem-rubyzip>=2.3.2 : archivers/rubygem-rubyzip
- rubygem-vagrant_cloud>=3.1.1<3.2 : sysutils/rubygem-vagrant_cloud
- rubygem-wdm>=0.1.1 : devel/rubygem-wdm
- rubygem-winrm>=2.3.6<3 : sysutils/rubygem-winrm
- rubygem-winrm-elevated>=1.2.3<2 : sysutils/rubygem-winrm-elevated
- rubygem-winrm-fs>=1.3.5<2 : filesystems/rubygem-winrm-fs
- ruby33 : lang/ruby33
- Patch dependencies:
-
- ruby33 : lang/ruby33
-
- There are no ports dependent upon this port
Configuration Options:- ===> The following configuration options are available for vagrant-2.4.1_3:
BASH=on: Install programmable completions for Bash
ZSH=on: Install programmable completions for zsh
===> Use 'make config' to modify these settings
- Options name:
- sysutils_vagrant
- USES:
- cpe ruby shebangfix
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 4
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
2.4.1_3
14 Aug 2025 05:20:41
 |
Matthias Fechner (mfechner) |
sysutils/vagrant: split into vagrant-gitlab that can be used together with
gitlab
Added a new port vagrant-gitlab that can be installed with gitlab on the same
host.
Currently I do not see another solution as other rubygem version that are
installed
by some ports are breaking gitlab and that was the reason to split this.
Some maintainers to do test their changes against all ports which made this step
necessary.
You can also install gitlab in a jail to fix these problems.
PR: 287926
(cherry picked from commit 2df3bbf5303028cd33818e1ffa45fa5efba44693) |
2.4.1_2
14 Aug 2025 05:20:41
|
Matthias Fechner (mfechner)
Author: Po-Chuan Hsieh |
sysutils/vagrant: Strip shared library
- Update version requirement of RUN_DEPENDS
- Sort RUN_DEPENDS
- Rename gemspec patch to patch-gemspec
- Bump PORTREVISION for package change
(cherry picked from commit 6ef55ffd377052b2838661bdb6a448280c66b101) |
2.4.1_1
31 Jul 2025 04:09:35
|
Matthias Fechner (mfechner) |
sysutils/vagrant: fix conflict with gitlab
PR: 287926
(cherry picked from commit cbfa75816205abd812cd2a83958032de898cf0f0) |
2.4.1
24 Jul 2025 13:45:18
|
Matthias Fechner (mfechner)
Author: John Hein |
sysutils/vagrant: update to 2.4.1
unbreak build with default ruby 3.3.
Changes: https://github.com/hashicorp/vagrant/blob/v2.4.1/CHANGELOG.md
PR: 288335
(cherry picked from commit a3257029a75010ef60657888bcff20974223e72d) |
Number of commits found: 4
|
As an Amazon Associate I earn from qualifying purchases.