summaryrefslogtreecommitdiffstats
path: root/build-root/vagrant/README.moved
diff options
context:
space:
mode:
authorEd Warnicke <eaw@cisco.com>2016-02-02 17:47:17 -0800
committerGerrit Code Review <gerrit@fd.io>2016-02-03 14:49:37 +0000
commiteeee9e2b1820ae1ca194ba0093d49519b66558f8 (patch)
tree6f1e1cbe26bd3cbef25c985acfb3b9328f941b70 /build-root/vagrant/README.moved
parentc28b4745911de6834a89343f40c35cafab59a706 (diff)
Switched vagrant for ~/git/vpp to /vpp
build-root/vagrant/Vagrantfile was always mounting the vpp into /vpp Now rather than cloning it and building, we just use it as mounted. In order to let folks know what happened, a README.moved is copied into the ~/git/vpp so folks know what happened. In addition to make it easier for folks to do commits from withing the vagrant, we install git-review, and copy in the users .gitconfig and .gnupg directory. A couple of notes about this. VMWare goes much much faster in all cases. Virtualbox is a bit slower in the very first run (without ccache). One of the benefits of using the mounted /vpp though is that after your first vagrant up, you always have access to the .ccache, as it lives outside the vagrant, and so in steady state everything is faster. Change-Id: I2cd2c28181b3d7e664240dfe2249b5be3f1b9241 Signed-off-by: Ed Warnicke <eaw@cisco.com>
Diffstat (limited to 'build-root/vagrant/README.moved')
-rw-r--r--build-root/vagrant/README.moved5
1 files changed, 5 insertions, 0 deletions
diff --git a/build-root/vagrant/README.moved b/build-root/vagrant/README.moved
new file mode 100644
index 00000000000..2bbf6564512
--- /dev/null
+++ b/build-root/vagrant/README.moved
@@ -0,0 +1,5 @@
+The location of the vpp code has moved from
+~/git/vpp
+To
+/vpp
+/vpp is a mount of the source code from outside the Vagrant, and should make it much easier to interact with the system.