It is only used by Vagrant, and could be pulled in from a separate repo as the first step of its provisioning, then proceeding as it does currently. It is the fourth largest directory in the repo (perhaps rising to third if updated), much of which is unnecessary (postgres, yum, nginx, etc). When it was originally added to the repo, it was around a dozen files; it's now a few thousand, and yet is not self-contained enough that it doesn't break when something external changes e.g. https://github.com/puphpet/puphpet/issues/1492 currently.
For full benefits, this could be accompanied by a rebase to remove it from the history. This could be accompanied by a move/removal of the unused googleappengine (largest directory) and uml-tests (third largest directory). (Second largest directory is images.)
It is only used by Vagrant, and could be pulled in from a separate repo as the first step of its provisioning, then proceeding as it does currently. It is the fourth largest directory in the repo (perhaps rising to third if updated), much of which is unnecessary (postgres, yum, nginx, etc). When it was originally added to the repo, it was around a dozen files; it's now a few thousand, and yet is not self-contained enough that it doesn't break when something external changes e.g. https://github.com/puphpet/puphpet/issues/1492 currently.
For full benefits, this could be accompanied by a rebase to remove it from the history. This could be accompanied by a move/removal of the unused
googleappengine
(largest directory) anduml-tests
(third largest directory). (Second largest directory is images.)