Package Details: vagrant-git 1.8.0.2.gf7bdcb1-1

Git Clone URL: https://aur.archlinux.org/vagrant-git.git (read-only)
Package Base: vagrant-git
Description: Build and distribute virtualized development environments
Upstream URL: http://vagrantup.com
Licenses: MIT
Conflicts: vagrant
Submitter: gtmanfred
Maintainer: jsteel
Last Packager: jsteel
Votes: 5
Popularity: 0.604692
First Submitted: 2013-09-03 20:50
Last Updated: 2015-12-22 09:50

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

jsteel commented on 2016-05-20 22:15

Why do you think it is a dependency? Please share what you are seeing.

coxa commented on 2016-05-20 20:37

Looks like that package have also libiconv dependency
Can any one chack that and add to dependecies?

jsteel commented on 2015-12-23 18:39

vagrant-substrate is in [community-testing] currently. So enable that repo or use vagrant-substrate-git from the AUR.

OldCrowEW commented on 2015-12-23 18:27

I am getting this error: error: target not found: vagrant-substrate

I see the dependencies but not sure why it isnt pulling them in properly.

EvanPurkhiser commented on 2014-04-12 00:31

unsetting my GEM_HOME fixed it. I'm not sure.. why

EvanPurkhiser commented on 2014-04-12 00:05

I'm getting a segmentation fault building this package: https://gist.github.com/EvanPurkhiser/10510865

flaccid commented on 2013-12-08 03:43

@gtmanfred Can you update to this? It fixes the issues and has some slight improvements https://github.com/flaccid/archlinux-packages/blob/master/vagrant-git/PKGBUILD. The sed command also needed a fix.

flaccid commented on 2013-12-08 03:12

Out of date because https://github.com/mitchellh/vagrant/blob/master/lib/vagrant/version.rb#L5 and license is MIT https://github.com/mitchellh/vagrant/blob/master/LICENSE. I do understand https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines - a better method can be used.

ido commented on 2013-10-25 22:56

License seems to be MIT.

gtmanfred commented on 2013-10-21 04:26

Unless you are going to tell my why you are marking it out of date, i am not going to change anything.

This currently still builds for me.

If you are marking it out of date because teh version number is 1.2.7, then you are doing it wrong, git and vcs pkgbuilds do not need to be updated because of new tags, that is what the pkgver() function is for and only people actually following it should be using the -git version